Support MaxDB for sequences #932
Merged
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
|
There is also problems here:
|
|
Could this PR be merged? |
|
Thanks! We're catching up on a set of fixes already in master, then will get this merged in. |
nvoxland
approved these changes
Dec 27, 2019
datical-jenkins
changed the title
datical-jenkins
changed the title
ro-rah
added
RiskLow
|
Placing Risk Low flag, I can see @nvoxland has approved these changes. |
…tke-master # Conflicts: # liquibase-core/src/main/java/liquibase/snapshot/jvm/UniqueConstraintSnapshotGenerator.java
suryaaki2
approved these changes
Jan 6, 2022
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.
MaxDB Liquibase Diff does not work for sequences as this database (liquibase-maxdb repo) is not included in the SequenceSnapshotGenerator.
(Query should be moved to the Database successor, anyways...)
(I also backported this to the 3.5.x branch.)
┆Issue is synchronized with this Jira Bug by Unito
┆fixVersions: Community 4.x