-
Notifications
You must be signed in to change notification settings - Fork 92
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
insert varchar column mismatch through INSERT INTO EXEC into a table #2017
insert varchar column mismatch through INSERT INTO EXEC into a table #2017
Conversation
Task: BABEL-2999 Signed-off-by: Zhibai Song <[email protected]>
503748e
to
db63e85
Compare
@@ -3047,6 +3069,210 @@ exec_stmt_insert_execute_select(PLtsql_execstate *estate, PLtsql_expr *query) | |||
return PLTSQL_RC_OK; | |||
} | |||
|
|||
static AttrMap* build_typecast_attrmap_by_position(TupleDesc indesc, TupleDesc outdesc, const char *msg) |
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.
It seems like this is very similar to build_attrmap_by_position()
. In that case, adding a special handling to the function can be better, if possible (either by adding a new hook or dialect check). If we copy engine's function, it will be not easy to adopt a new major versions when there are some changes in the original function.
2d20e6c
into
babelfish-for-postgresql:BABEL_3_X_DEV
Previously insert exec implement didn't consider the type cast during execution, this fix has add a implicit type cast between insert execution and exec execution if the type is mismatched. Engine pr : babelfish-for-postgresql/postgresql_modified_for_babelfish#256 Task: BABEL-2999, BABEL-4426 Signed-off-by: Zhibai Song <[email protected]>
Previously insert exec impl didn't consider the type cast during execution, this fix has add a implicit type cast between insert execution and exec execution if the type is mismatched.
Task: BABEL-2999
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.