fix!: EXPOSED-546 [H2] Column with Json default value can not be used as databaseGenerated #2241
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.
That bug I found when I was working on disabling sending all the default parameters explicitly in insert statements.
The main reason, before changes the DDL definition of the columns was looking like
JSON DEFAULT '{"name":"name","team":"team"}'
, and it was recognized string, so the new entry hadjson string
instead ofjson object
. After changes DDL looks likeDEFAULT JSON '{"name":"name","team":"team"}'
Type of Change
Updates/remove existing public API methods:
Affected databases:
Related Issues
EXPOSED-546 [H2] Column with Json default value can not be used as databaseGenerated