Restore START sequence option in PostgreSQL mode and improve documentation of MSSQLServer mode #3760
+35
−7
Conversation
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.
<sequence generator start with option>in PostgreSQL doesn't requireWITHkeyword and can be specified asSTART 1. It was also possible in historic versions of H2, but modern versions don't allow this syntax. Possibility to use it is restored here only for PostgreSQL compatibility mode. Closes H2 2.x cannot read PostgreSQL-style sequence generator start with option without WITH keyword #3675.MSSQLServercompatibility mode now suggests;DATABASE_TO_UPPER=FALSE;CASE_INSENSITIVE_IDENTIFIERS=TRUEfor better compatibility.AssertionErrorinFileStore.serializeAndStore()is fixed. Closes AssertionError in mvstore.FileStore.serializeAndStore #3642.