-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The database default created by Migrations for primitive collections mapped to JSON is invalid #32972
Labels
area-json
area-migrations
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
Servicing-approved
type-bug
Milestone
Comments
maumar
added a commit
that referenced
this issue
Feb 9, 2024
…ive collections mapped to JSON is invalid Problem was that when adding new required column to an existing table we always need to provide default value (to fill the values for rows already in the table). For collection of primitives that get map to json we should be setting the value to empty JSON collection, i.e. '[]' but we were not doing that. Fixes #32972
maumar
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Feb 9, 2024
maumar
added a commit
that referenced
this issue
Feb 9, 2024
…ive collections mapped to JSON is invalid Problem was that when adding new required column to an existing table we always need to provide default value (to fill the values for rows already in the table). For collection of primitives that get map to json we should be setting the value to empty JSON collection, i.e. '[]' but we were not doing that. Fixes #32972
maumar
added a commit
that referenced
this issue
Feb 10, 2024
…ive collections mapped to JSON is invalid (#33039) Problem was that when adding new required column to an existing table we always need to provide default value (to fill the values for rows already in the table). For collection of primitives that get map to json we should be setting the value to empty JSON collection, i.e. '[]' but we were not doing that. Fixes #32972
reopening for patch |
maumar
added a commit
that referenced
this issue
Feb 10, 2024
…ive collections mapped to JSON is invalid Problem was that when adding new required column to an existing table we always need to provide default value (to fill the values for rows already in the table). For collection of primitives that get map to json we should be setting the value to empty JSON collection, i.e. '[]' but we were not doing that.
maumar
added a commit
that referenced
this issue
Feb 10, 2024
maumar
added a commit
that referenced
this issue
Feb 11, 2024
maumar
added a commit
that referenced
this issue
Feb 12, 2024
maumar
added a commit
that referenced
this issue
Mar 5, 2024
…ive collections mapped to JSON is invalid (#33048) Problem was that when adding new required column to an existing table we always need to provide default value (to fill the values for rows already in the table). For collection of primitives that get map to json we should be setting the value to empty JSON collection, i.e. '[]' but we were not doing that.
merged to release/8.0, closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-json
area-migrations
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
Servicing-approved
type-bug
See #32896 (comment)
The text was updated successfully, but these errors were encountered: