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
Migration to 2.3.2 fails with "duplicate column name: id" #346
Comments
Thanks for bringing this up. I was able to reproduce the error. It occurs while attempting to migrate the Some digging led to the following GORM issue, which describes the exact same scenario: go-gorm/gorm#5175. There seems to be a bug in GORM which we'll have to wait for to get fixed. In the meanwhile, you should be able to work around this by setting |
@muety setting |
Sorry for the stupid question, how can I run customized config.yml when using Docker? |
Use the respective environment variable (with |
I found that the mentioned upstream bug is not actually the cause for this issue, instead it's related to go-gorm/sqlite#87. I'll push a fix soon. |
This is not fixed for me. I must use |
What exact errors do you get? |
The same as the one in the description of this issue. |
Can you please post the result of running the following query on your SQLite database? select * from sqlite_schema |
|
Can't reproduce this. Are you on version 2.3.4? |
Oh, no. It is 2.3.2. My bad. |
I fixed it, thanks for being with me @muety! |
Describe the bug
System information
Please provide information on:
The text was updated successfully, but these errors were encountered: