-
Notifications
You must be signed in to change notification settings - Fork 93
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
Default tags to [] in the database #46
Labels
needs db migration
Fixing this issue would require a new database migration
Comments
bgentry
added
the
needs db migration
Fixing this issue would require a new database migration
label
Nov 21, 2023
@brandur thought about this more today and realized now that we've shipped this would require a new DB migration to be added. Maybe we want to hold off and batch it together with other such changes? |
@bgentry Only other option is to YOLO and have a policy that first day installs are going to need a remigrate. TBH, I think that's okay personally, but has to be done fast. |
bgentry
added a commit
that referenced
this issue
Nov 21, 2023
bgentry
added a commit
that referenced
this issue
Nov 21, 2023
bgentry
added a commit
that referenced
this issue
Nov 22, 2023
This adds a new migration v3 to adjust the tags column to ensure it's never null, which helps simplify client implementations by not making them deal with both null and empty array values. Fixes #46.
bgentry
added a commit
that referenced
this issue
Nov 22, 2023
This adds a new migration v3 to adjust the tags column to ensure it's never null, which helps simplify client implementations by not making them deal with both null and empty array values. Fixes #46.
bgentry
added a commit
that referenced
this issue
Nov 22, 2023
This adds a new migration v3 to adjust the tags column to ensure it's never null, which helps simplify client implementations by not making them deal with both null and empty array values. Fixes #46.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From #44 (comment):
The text was updated successfully, but these errors were encountered: