-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
Check if column exist before rename if exist, just return with no error #17870
Conversation
We should also drop the And more comments about why we need this hacky patch. |
Since it has been renamed, if |
But the users do meet the bug that |
done. |
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.
LGTM. But I still think we had better comment this patch about why we need it
. Otherwise developers in future will be confused why we wrote the strange logic today.
I will add some comments there. |
It's due to them running the install page when the db already exists. |
#17486 will prevent this issue. It's just not been in a release. |
26c470b
to
9d5830b
Compare
make L-G-T-M work |
…or (go-gitea#17870) * Check if column exist before rename if exist, just return with no error * Also check if errors column exist * Add comment for migration * Fix sqlite test
…or (go-gitea#17870) * Check if column exist before rename if exist, just return with no error * Also check if errors column exist * Add comment for migration * Fix sqlite test
Some people upgrade failed because of duplicated column message on task. Don't know how it addressed, but this PR could prevent the failed upgrade.