better detection/extraction of existing sequences in H2 #505
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
darkv
added a commit
that referenced
this pull request
Jan 15, 2014
better detection/extraction of existing sequences in H2
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.
When EOF needs to generate new primary keys it uses sequences that follow a certain naming schema. If that sequence has not yet been created by EOF it will first check if there is already a sequence it can use before creating its own.
Instead of extracting the name of an existing sequences from the SQL expression stored in the information schema get it directly from the SEQUENCE_NAME field or alternatively extract it from the column with the default value definition.