Fix syntax error issue while using [primary] column name in DML/DDL statements #3132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tatements (babelfish-for-postgresql#3131) This commit resolves the syntax error issue that occurs when using '[primary]' as a column name in DML and DDL statements. Task: BABEL-5422 Issue: babelfish-for-postgresql#3127 Signed-off-by: Sumit Jaiswal [email protected]
Pull Request Test Coverage Report for Build 11912859714Details
💛 - Coveralls |
KushaalShroff
approved these changes
Nov 19, 2024
shardgupta
merged commit d0aa61c
into
babelfish-for-postgresql:BABEL_4_4_STABLE
46 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This commit resolves the syntax error issue that occurs when using '[primary]' as a column name in DML and DDL statements.
Signed-off-by: Sumit Jaiswal [email protected]
Issues Resolved
Task: BABEL-5422
Issue: #3127
Test Scenarios Covered
Use case based - Yes
Boundary conditions - Yes
Arbitrary inputs - NA
Negative test cases - NA
Minor version upgrade tests - NA
Major version upgrade tests - NA
Performance tests - NA
Tooling impact - NA
Client tests - NA
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.