-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Attempt to make "require shares fields" migration safer/more reliable #19619
Conversation
🦋 Changeset detectedLatest commit: 4d37132 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Co-authored-by: Azri Kahar <42867097+azrikahar@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am unable to repro the original issue but the code looks good
…directus#19619) Co-authored-by: Azri Kahar <42867097+azrikahar@users.noreply.github.com>
After the last correction of the "require shares fields" migration in #19407, it seems that there are still MySQL instances that struggle with this migration (see #19399).
Unfortunately this could not be reproduced so far, so here's an attempt to make the migration a bit safer/more reliable:
ALTER TABLE
statements, because depending on the engine it may not be supported to drop & recreate in the same statement.Closes #19399 (we'll reopen if issue should still not be solved)