-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Handle case sensitive primary key names in dropPrimaryKey for postgresql #1974
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
Merged
Conversation
This file contains hidden or 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
@nvoxland @suryaaki2 Any progress on this? It needs this additional update to pass the tests:
As I wrote in #1933 (comment), it otherwise works fine. |
suryaaki2
approved these changes
Jul 27, 2021
@nvoxland @suryaaki2 Anything I can do to help speed this up? |
@nvoxland @suryaaki2 Any chance this will get merged & released soon'ish? It's really blocking us from updating… |
It will be going out in the upcoming 4.6.0 release |
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.
Fixes #1933
Dev Handoff Notes (Internal Use)
Links
Testing
Dev Verification
Liquibase command 'update' was executed successfully.
Test Requirements (Liquibase Internal QA)
Manual Tests
Use the changelog attached to this ticket to run your tests against a Postgres database.
liquibase update --changelog-file lb1976-changelog.xml --labels createTable
Verify update of a dropPrimaryKey with an auto-generated, camelCase PK name is successful._
liquibase update --changelog-file lb1976-changelog.xml --labels dropAutoNamedPK
Verify update of a addPrimaryKey with a camelCase named PK is successful._
liquibase update --changelog-file lb1976-changelog.xml --labels addNamedPK
Verify update of a dropPrimaryKey with a camelCase named PK is successful._
liquibase update --changelog-file lb1976-changelog.xml --labels dropNamedPK
Automated Test Requirements
Validate that dropPrimaryKey does not fail due to camelCasing of the autogenerated PK name.
┆Issue is synchronized with this Jira Bug by Unito