Configure EclipseLink for automatic schema migration #456
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.
Description
After #438 , it was reported that users with an existing metastore might not see the new columns get added to the metastore. This PR configures EclipseLink (via the default
persistence.xml) to automatically add new columns when they should appear in the metastore.Fixes #450
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
With this PR, I have walked through the steps described in #450, and tests are now (mostly) passing: