-
Notifications
You must be signed in to change notification settings - Fork 93
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
Display unmapped schema names in error messages #3095
base: BABEL_4_X_DEV
Are you sure you want to change the base?
Display unmapped schema names in error messages #3095
Conversation
Previously, Babelfish displays the mapped schema names in error messages. This commit implements a hook function remove_db_name_in_schema and adds test cases. Task: BABEL-2961 Signed-off-by: Chenxiao Wang <chxwang@amazon.com>
Task: BABEL-2961 Signed-off-by: Chenxiao Wang <chxwang@amazon.com>
711abac
to
de58d72
Compare
Pull Request Test Coverage Report for Build 11802489209Details
💛 - Coveralls |
Signed-off-by: Chenxiao Wang <chxwang@amazon.com>
Signed-off-by: Chenxiao Wang <chxwang@amazon.com>
Signed-off-by: Chenxiao Wang <chxwang@amazon.com>
f3ec631
to
c6851f9
Compare
* @return - unmapped schema name char * | ||
*/ | ||
static const char * | ||
remove_db_name_in_schema(const char *schema_name) |
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.
Should compare BBF & SQL Server error messages of cross-db queries. Do schema names in cross-db queries need to be mapped as well?
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.
No, this fucntion works only if the input schema_name
has current db name as prefix. So if I query another db, nothing will change in the error message
Description
Previously, Babelfish displays the mapped schema names in error messages. This commit implements a hook function remove_db_name_in_schema and adds test cases. Original unmapped name will be displayed with this commit.
Issues Resolved
BABEL-2961
Test Scenarios Covered
Use case based - ✅
Boundary conditions - NA
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.