Fixed case expression when one of the branch is NUMERIC and other is of EXACT NUMERIC. #3607
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.
Issues
CASE statement doesn't gives correct typmod when one of the branch is numeric and other is of exact numeric. The precision is being set 5 and scale is set to 4 in babelfish.
So expected result (123.0000) won't fit in Numeric(5,4). So we need to figure out correct precision and scale in this case.
Changes made to fix the issues
In the tsql_select_common_typmod hook, allowed exact numeric types for calculating correct precision and scale.
cherry-pick from #3584
Task: BABEL-5678
Authored-by: yashneet vinayak [email protected]
Signed-off-by: yashneet vinayak [email protected]
Test Scenarios Covered
**Use case based -**YES
**Boundary conditions -**YES
**Arbitrary inputs -**YES
**Negative test cases -**YES
Minor version upgrade tests -
Major version upgrade tests -
Performance tests -
Tooling impact -
**Client tests -**YES
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.