-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
SQLite to Postgres migration script has errors #2222
Comments
I'm looking into a similar problem for ash, which is full of:
...from a DB which was originally a sqlite->postgres migration. |
...actually, this is a red herring; ash's problems are due to _persist_events_txn trying to insert null state groups for reasons, not DB corruption (filed as #2730) |
Wonder if these are related? This is what I hit today:
Really curious if there's a fix. I'm having forward extremity issues once again, and the SQL in #1760 doesn't seem to work on SQLite. Thanks! |
I found the same issue yesterday night: |
this seems sufficiently old that it doesn't seem useful any more |
I tried to migrate my database from SQLite to Postgres earlier today, and ran into various issues relating to duplicate keys violating various constraints, causing the import script to crash. A couple examples are below, but running the script multiple times will generally find different invalid rows.
Validating the SQLite confirms that there's nothing wrong with the DB:
I'm mostly just interested in getting the thing to Postgres for performance reasons, so any kind of update to the script that'll allow me to continue importing instead of just crashing would be greatly appreciated.
Also, someone should (eventually) make the constraints on both databases identical (where possible), so that valid SQLite files aren't rejected by Postgres.
[edited by @richvdh 2018/02/28 to format logs sanely]
The text was updated successfully, but these errors were encountered: