#29182: SQLite database migration breaks ForeignKey constraint, leaving <table_name>__old in db schema ----------------------------------+------------------------------------ Reporter: ezaquarii | Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 2.0 Severity: Release blocker | Resolution: Keywords: sqlite migration | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ----------------------------------+------------------------------------
Comment (by Simon Charette): Cannot reproduce with `SQLite 3.23.1` and `3.24.0 2018-06-04 14:10:15` either, I'll try to get my hands on 3.26+ tomorrow. Could you provide the output of {{{#!python import sqlite3 sqlite3.connect('file::memory:').cursor().execute('PRAGMA compile_options').fetchall() }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:16> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.21ed72bf7d66ce32d7ce8ee8596992b3%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.