Fix SQL generation when having a column defined with startWith and incrementBy in Postgres #5629
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
…ns in postgres sql generation. - Test updated. - Integration test data added to validate this scenario.
MalloD12
changed the title
filipelautert
approved these changes
Mar 4, 2024
rberezen
approved these changes
Mar 4, 2024
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.
Impact
Description
getAutoIncrementClausewas returning a wrong SQL code when bothincrementByandstartWithwere defined for a column, an extra,was being added resulting in a SQL syntax error. This is a fix to that issue, updating an existent test for it and adding a new changeset with these two clauses together to be executed in a Postgres DB.Fixes #4149
Things to be aware of
Things to worry about
Additional Context