-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Migrate superset db from sqlite to postgres fails key constraints #2475
Comments
I am also getting an issue when I attempt to migrate my Postgres with the most recent update. I am getting the following errors when I run superset db migrate. The db is hosted on RDS and was working prior to the migration.
|
This looks like more of an alembic / flask-migrate issue rather than a superset one |
Do you have any tips on how to address it? |
Notice: this issue has been closed because it has been inactive for 383 days. Feel free to comment and request for this issue to be reopened. |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.15.4
Expected results
I've previously migrated data from one sqlite to a fresh new sqlite database with no issues. Now when I've ported the raw table data from sqlite into postgres, I get primary key errors when trying to create new tables /slices/dashboards through superset directly post migration. I checked and the primary keys in postgres aren't sequences that need to be reset. So there must be some other indexing happening with superset directly.
Is there a way to reset the index/counters?
I've checked and each attempt to add a table will increment the ID even if it fails. Eventually it works, but fails due to column IDs not incrementing.
Actual results
Steps to reproduce
The text was updated successfully, but these errors were encountered: