#30033: SQLite schema editor should use the documented to emulate table
alterations
on SQlite3.
-------------------------------------+-------------------------------------
Reporter: Simon | Owner: Simon Charette
Charette |
Type: | Status: assigned
Cleanup/optimization |
Component: | Version: master
Migrations |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In the light of #29182 SQLite's main author mentioned that we should
conform to the documented procedure to emulate table alterations on
SQlite3.
Right now the [https://www.sqlite.org/lang_altertable.html#caution
SQLite's schema editor follows a procedure documented as incorrect] and
prevents usages of the SQLite 3.26 improvements regarding table and column
renames while foreign key constraints are disabled.
--
Ticket URL: <https://code.djangoproject.com/ticket/30033>
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/052.e32da1e434800fa57ae32f3ef8b77c01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
