DDl-Refactor: Add DB2 Reorg support and history support #2596
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
|
Well done - a very big effort here !! |
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.
This PR moves Ebean to a state where it has working DB2 migration (with proper reorg-table statements. See #2556)
We have also a working history now: DB2: HistorySupport added
Unfortunately, DB2 needs an exact copy of the history table. So it is not allowed to have
not nullcolumn in live table andnullcolumn in history table as it is common in trigger based history@rbygrave There is currently a hack
syncExact = platformDdl.getPlatform().isPlatform(Platform.DB2)for DB2I would change that for all platforms. This means:
nulltonot null, you have to migrate also the null values in history table.Docker DB2 test is passing now