-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added escape hatch for IDENTITY() in select into #2055
Added escape hatch for IDENTITY() in select into #2055
Conversation
else | ||
{ | ||
ereport(ERROR, | ||
(errcode(ERRCODE_SYNTAX_ERROR), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added here because contrib/babelfishpg_tsql/src/tsqlUnsupportedFeatureHandler.cpp has no check for Into() yet. Can be done through that also but will need more changes
Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
Updated file BABEL-UNSUPPORTED, Added escape_hatch_identity_function Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
8d7289b
to
0873d84
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
9237ce8
into
babelfish-for-postgresql:BABEL_3_X_DEV
…resql#2055) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]> (cherry picked from commit 9237ce8)
…ABLE (#2069) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]> (cherry picked from commit 9237ce8)
…resql#2055) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
…resql#2055) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
…resql#2055) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
…resql#2055) Need this because identity column will always be the last one in table if created using a select into statement Task: BABEL-539 Signed-off-by: Deepakshi Mittal <[email protected]>
Added escape_hatch_identity_function for IDENTITY() in select into
Need this because identity column will always be the last one in table if created using a select into statement
Task: BABEL-539 and BABEL-4388
Description
Added escape_hatch_identity_function for IDENTITY() in select into
Related pr: #1967
Issues Resolved
BABEL-539, BABEL-4388
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.