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

2018-05-08 Thread Informatico Neurodesarrollo
Check 1.11 to 2.0 upgrade. You already checked the project configuration and make migrations ?, it could be changed with the upgrade!!! I will hope help you. PD I'm a beginner in Django. El 06/05/18 a las 23:38, Michael Gauland escribió: Just in case anyone else runs into this, I fixed it by s

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
I've got a project that's been developed using django 1.11. I've tried upgrading to 2.0, but now I'm getting an error I haven't been able to track down. My database engine is sqlite3. I have three database files: - db.sqlite3 is the default. This is the only one that django manages, and the o