Skip to content

Fix: return NoData for Describe (Portal) before Execute on empty statement#5143

Merged
renecannao merged 2 commits intov3.0from
v3.0_fix-describe-portal-nodata-empty-query
Oct 14, 2025
Merged

Fix: return NoData for Describe (Portal) before Execute on empty statement#5143
renecannao merged 2 commits intov3.0from
v3.0_fix-describe-portal-nodata-empty-query

Conversation

@rahim-kanji
Copy link
Collaborator

Summary

Fixes an issue where Describe (Portal) does not return a NoData response when sent before Execute if the prepared statement was created with an empty query string.

Details

  • Extended query flow with empty query string: Parse (empty statement) -> Bind -> Describe (Portal) -> Execute.
  • Previously, Describe (Portal) returned nothing if called before Execute.
  • Now, the server correctly returns a NoData response in this case, making behavior consistent with protocol expectations.

query)

Now the server returns the expected NoData response in this case,
consistent with protocol behavior.
@gemini-code-assist
Copy link

Summary of Changes

Hello @rahim-kanji, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a specific edge case in the PostgreSQL extended query protocol where Describe (Portal) was not behaving as expected for prepared statements with empty query strings. The change ensures that the server responds with a NoData message in such situations, aligning its behavior with the protocol specification and improving client-server communication consistency. New tests have been introduced to verify this corrected behavior.

Highlights

  • Bug Fix: Describe (Portal) for Empty Statements: Resolved an issue where Describe (Portal) would not return a NoData response when used with a prepared statement containing an empty query string, specifically when called before Execute.
  • Protocol Compliance: The server now correctly sends a NoData message in this scenario, ensuring adherence to PostgreSQL protocol expectations for extended query flow.
  • New Test Cases: Added comprehensive test cases to validate the new behavior, covering both scenarios where Describe (Portal) is used and not used with empty prepared statements.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes an issue where Describe (Portal) on an empty statement did not return a NoData response. The logic change in PgSQL_Connection.cpp is sound, and the accompanying tests in pgsql-extended_query_protocol_test-t.cpp effectively verify the fix and a control case. My review includes a minor suggestion to improve code readability in the fix, and points out a few copy-paste errors in the new tests, such as a redundant check and an incorrect error message.

@rahim-kanji rahim-kanji force-pushed the v3.0_fix-describe-portal-nodata-empty-query branch from 2a610f9 to cd2640f Compare October 3, 2025 21:01
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 3, 2025

@renecannao renecannao merged commit 2c9cea0 into v3.0 Oct 14, 2025
147 of 154 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants