Remove Sequence batching in favour of always using JPA increment 50#1966
Open
rbygrave wants to merge 2 commits into
Open
Remove Sequence batching in favour of always using JPA increment 50#1966rbygrave wants to merge 2 commits into
rbygrave wants to merge 2 commits into
Conversation
Also remove h2sqldb in favour of always using H2
rbygrave
force-pushed
the
feature/removeSequenceBatching
branch
from
be40972 to
08d241d
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Also remove h2sqldb in favour of always using H2
This feature is expected to only be used by older Ebean users with DB2 and Oracle with sequences as
increment by 1. It is not expected to impact anyone else - Postgres, MySql, SQLServer etc.