#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
Reporter: ezaquarii | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 2.1
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):
Hello Chris,
I don't think the approach of the patch
https://code.djangoproject.com/ticket/29182#comment:12 will work.
Could you give
https://github.com/django/django/compare/master...charettes:ticket-29182-pragma
a run against the test suite on SQLite 3.26.
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:23>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.6f68e3162edbf66900085cbb653a954a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
