Skip to content
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

Closed
ajcvickers opened this issue Jan 31, 2024 · 2 comments · Fixed by #33039
Assignees
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

@ajcvickers
Copy link
Contributor

See #32896 (comment)

@ajcvickers ajcvickers self-assigned this Jan 31, 2024
@ajcvickers ajcvickers assigned maumar and unassigned ajcvickers Jan 31, 2024
@ajcvickers ajcvickers added this to the 8.0.x milestone Jan 31, 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 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
@maumar
Copy link
Contributor

maumar commented Feb 10, 2024

reopening for patch

@maumar maumar reopened this Feb 10, 2024
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.
@ajcvickers ajcvickers modified the milestones: 8.0.x, 8.0.4 Feb 15, 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.
@maumar
Copy link
Contributor

maumar commented Mar 5, 2024

merged to release/8.0, closing

@maumar maumar closed this as completed Mar 5, 2024
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
Projects
None yet
2 participants