fix: validate named parameters are present in arguments#730
fix: validate named parameters are present in arguments#730maishivamhoo123 wants to merge 2 commits intogoogleapis:mainfrom
Conversation
Summary of ChangesHello @maishivamhoo123, 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 introduces crucial validation for named parameters in SQL statements, preventing a previous issue where missing parameters would silently default to Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request effectively addresses the critical issue of missing named parameter validation in SQL statements, preventing silent NULL assignments and improving query reliability. The changes in stmt.go introduce a clear error message when a parameter is not found, and the new test case in driver_test.go provides good coverage for this validation. The dependency updates in go.sum are standard and expected.
|
@bhatt4982 @olavloite Sir can you please review the changes? |
Named parameters in the SQL string were not translated to PostgreSQL-style query parameters before sending these to Spanner. This made it impossible to use named query parameters with PostgreSQL-dialect databases. This change also fixes an issue that PostgreSQL-style query parameters had to be used in order, and an issue that using a wrong value for a named parameter would not cause an error, and instead just silently send a null value for the parameter to Spanner. Fixes #738 Fixes #601 Fixes #730
Named parameters in the SQL string were not translated to PostgreSQL-style query parameters before sending these to Spanner. This made it impossible to use named query parameters with PostgreSQL-dialect databases. This change also fixes an issue that PostgreSQL-style query parameters had to be used in order, and an issue that using a wrong value for a named parameter would not cause an error, and instead just silently send a null value for the parameter to Spanner. Fixes #738 Fixes #601 Fixes #730
Named parameters in the SQL string were not translated to PostgreSQL-style query parameters before sending these to Spanner. This made it impossible to use named query parameters with PostgreSQL-dialect databases. This change also fixes an issue that PostgreSQL-style query parameters had to be used in order, and an issue that using a wrong value for a named parameter would not cause an error, and instead just silently send a null value for the parameter to Spanner. Fixes #738 Fixes #601 Fixes #730
Named parameters in the SQL string were not translated to PostgreSQL-style query parameters before sending these to Spanner. This made it impossible to use named query parameters with PostgreSQL-dialect databases. This change also fixes an issue that PostgreSQL-style query parameters had to be used in order, and an issue that using a wrong value for a named parameter would not cause an error, and instead just silently send a null value for the parameter to Spanner. Fixes googleapis#738 Fixes googleapis#601 Fixes googleapis#730
Description
This PR addresses an issue where named parameters present in a SQL statement were not being validated against the provided arguments. Previously, if a user omitted a parameter, the driver would remain silent and Spanner would default the value to
NULL, often leading to incorrect query results or unexpected behavior.Changes
stmt.goto validate that all named parameters parsed from the SQL string exist in the providedargs.NULLassignments.driver_test.goto ensure validation works for various edge cases.Testing
I have verified these changes by running the test suite in short mode:
go test -v -short ./...PASS(specificallyTestQuery_NamedParameterValidation)Related Issue
Fixes #709