#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
Reporter: ezaquarii | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Release blocker | Resolution: fixed
Keywords: sqlite migration | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Carlton Gibson <carlton.gibson@…>):
In [changeset:"894cb13779e6d092974c873bd2cf1452554d2e06" 894cb13]:
{{{
#!CommitTicketReference repository=""
revision="894cb13779e6d092974c873bd2cf1452554d2e06"
Refs #29182 -- Stopped relying on legacy alter table semantic on SQLite
3.26+.
SQLite 3.26 changed the behavior of table and column renaming operations
to
repoint foreign key references even if foreign key checks are disabled.
This makes the workarounds in place to simulate this behavior unnecessary
on
SQLite 3.26+. Refs #30033.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:41>
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.c0ad40f8d07505d79c463294142ed0df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
