-
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
Adding fix for edge cases in Space function #2807
Merged
jsudrik
merged 6 commits into
babelfish-for-postgresql:BABEL_3_X_DEV
from
amazon-aurora:babel_4811_space_function_fix_3_x
Jul 30, 2024
Merged
Adding fix for edge cases in Space function #2807
jsudrik
merged 6 commits into
babelfish-for-postgresql:BABEL_3_X_DEV
from
amazon-aurora:babel_4811_space_function_fix_3_x
Jul 30, 2024
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
…#2742) Currently for string function SPACE() we only handle positive integers and throws error for input 0 or negative number. This commit will handle those edge cases and when a negative number is passed we will return NULL and when 0 is passed we will return an empty string. Additionally, this commit adds handling when input integer is greater than 8000. Task: BABEL-4811 Signed-off-by: Tanya Gupta <[email protected]>
Signed-off-by: Tanya Gupta <[email protected]>
schedule file Signed-off-by: Tanya Gupta <[email protected]>
Pull Request Test Coverage Report for Build 10158728727Details
💛 - Coveralls |
tanyagupta17
changed the title
Adding fix for edge cases in Space function in 3_X
Adding fix for edge cases in Space function
Jul 30, 2024
Signed-off-by: Tanya Gupta <[email protected]>
rohit01010
approved these changes
Jul 30, 2024
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
jsudrik
approved these changes
Jul 30, 2024
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.
Approved.
jsudrik
merged commit Jul 30, 2024
ad03399
into
babelfish-for-postgresql:BABEL_3_X_DEV
42 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
Currently for string function SPACE() we only handle positive integers and throws error for input 0 or negative number. This PR will handle those edge cases and when a negative number is passed we will return NULL and when 0 is passed we will return an empty string. Additionally, this commit adds handling when input integer is greater than 8000.
Cherry-picked from: #2742
Signed-off-by: Tanya Gupta [email protected]
Issues Resolved
BABEL-4811
Test Scenarios Covered
Use case based - YES
Boundary conditions - YES
Arbitrary inputs - YES
Negative test cases - YES
Minor version upgrade tests - YES
Major version upgrade tests - YES
Performance tests - NO
Tooling impact - NO
Client tests - NO
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.