fix broken migration #163
Merged
fix broken migration #163
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
A recent change in the auth.identities table made the following changes: 1. The id column was renamed to provider_id. 2. A new id column which should be a random uuid. This change broke our "fix_auth_schema_values" migration. To fix it we updated the insert statement to include email as the provider id value and a random uuid as the id. Since for email provider the provider_id should be email id in lowercase we added a new migration "update_provider_id" to update the provider_id column to the email column value. Updating an older migration is bad practice but I don't think we have any other option now.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
olirice
approved these changes
Jan 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A recent change in the
auth.identitiestable made the following changes:idcolumn was renamed toprovider_id.idcolumn which should be a random uuid.This change broke our "fix_auth_schema_values" migration. To fix it we updated the insert statement to include email as the
provider_idvalue and a random uuid as theid. Since for email provider theprovider_idshould be email id in lowercase we added a new migration "update_provider_id" to update theprovider_idcolumn to theemailcolumn value.Updating an existing migration is bad practice but I don't think we have any other option now.