Re: Upgrading from 1.11 to 2.0: "sqlite3.OperationalError: no such table"

2018-05-06 Thread Michael Gauland
Just in case anyone else runs into this, I fixed it by specifying db_contraint=False for foreign keys which cross databases. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send

Upgrading from 1.11 to 2.0: "sqlite3.OperationalError: no such table"

2018-05-03 Thread Michael Gauland
curve.save() If I don't try to save the curve, the test passes. The save() call fails with: sqlite3.OperationalError: no such table: main.slat_location Again, this all works with django 1.11.13. I've tried creating a fresh database, and making new migrations, but that hasn't h