-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Migrations bug #2206
Comments
I think 3 is must and if does not have migration, this should be fixed |
@andreynering has contributed |
I'd like option 1. |
@lunny If we switch to that we'll loose all hopes of migrating from Gogs to Gitea in the future |
@Bwko that can make problems if you are upgrading from version where later column has been added to structure and in later removed and there is migration that converts it data to either other column or table for example |
@lafriks yes, but that's a bug. |
If we use the Xorm migrate package, even them we would have to keep existing migrations for a while. Also, this don't solve the migration from Gogs problem. Also keep in mind it is not as stable as the Gorm version since it don't have recent fixes, etc. There's no easy solution for this. |
@lafriks You're right, then we need to go for solution 3 |
I was just bit by this issue, and can't upgrade one of my older Gogs instances to the new Gitea 1.2-rc1. |
@lunny if this bug prevents upgrading from Gogs it should be considered of upmost importance, why postponing fix to 1.3.0 ? Maybe I misunderstood the severity and db 16 is not a supported Gogs version ? |
I was upgrading from |
From docs:
Gogs versions up to 0.9.146 (db schema version 15) can be smoothly upgraded to Gitea.
So yes, it should be supported
|
- This also means that if one of the test fails, it will actually propagate to make and subsequently fail the test. - Remove the 'delete duplicates issue users' code, I checked this against my local development database (which contains quite bizarre cases, even some that Forgejo does not like), my local instance database and against Codeberg production and they all yielded no results to this query, so I'm removing it thus resolving the error that the delete code was not compatible with Mysql. - Sync all tables that are requires by the migration in the test. - Resolves go-gitea#2206 (cherry picked from commit 8e02be7e89a76ccbc3f8a58577be0fcc34e1469e) (cherry picked from commit 006f06441645d864fc27ca30352367b3afafc5bb)
When migrating from gogs db version 16 the following happens:
Migrate v37.go uses the latest
models.User
. Some of themodels.User
columns do not exists, likekeep_email_private
. Resulting in the following error:ERROR: column "keep_email_private" does not exist
.After all migrations are done xorm "magically" creates the missing columns.
Solutions:
id & full_name
The text was updated successfully, but these errors were encountered: