#37006: Attempting to recreate the PK in a model with no other fields generates
a
migration that crashes on SQLite
-------------------------------------+-------------------------------------
Reporter: Carol Naranjo | Owner: Carol
| Naranjo
Type: Bug | Status: assigned
Component: Migrations | Version: 6.0
Severity: Normal | Resolution:
Keywords: sqlite, migrations | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* needs_better_patch: 0 => 1
Comment:
Thanks for the patch Carol, excited to hear you are part of Djangonauts!
I left some comments on the PR. It is heading in the right direction but
it should offer the possibility of a rename and not force it when a
primary is changed because we won't be able to support all field type
alterations so we need an escape hatch to allow the users to drop the
field and create a new one when it's the case.
--
Ticket URL: <https://code.djangoproject.com/ticket/37006#comment:10>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019d8206d1fa-80482860-f2b1-48ba-be74-e7aba64602d1-000000%40eu-central-1.amazonses.com.
