bugfix in migration of collection subscriptions #361
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
…_subscription_table.sql
…_subscription_table.sql
…_subscription_table.sql
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.
In DSpace 7.5 a bug in the migration of collection subscriptions was fixed (
dspace_object_idandtypecolumns in tablesubscriptionwere not filled properly) 👉 DSpace@b4f7ebfThis change was added to the CRIS code base, but later on it was (accidentally?) removed in DSpace CRIS in H2 and Postgres migration scripts.
This PR adds the missing changes to the Flyway migration scripts. Furthermore, it removes outdated subscription migration scripts which affect DSpace 7.0