#37006: Attempting to recreate the PK in a model with no other fields generates
a
migration that crashes on SQLite
------------------------------------+------------------------------------
Reporter: Carol Naranjo | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 6.0
Severity: Normal | Resolution:
Keywords: sqlite, migrations | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by Carol Naranjo):
Replying to [comment:1 Jacob Walls]:
> Thanks, reproduced at f6167b8bc881babd19b67c004e8f37954afc192e. Looks
like another circumstance that manifests the failure described in #24424.
Hi Jacob, can you double check the commit link? it seems unrelated.
---
Replying to [comment:2 Simon Charette]:
>
> There might be a way to approach this at the auto-detector level by
turning a removal and addition of a `Field(primary_key=True)` with a
different name as a `[AlterField, RenameField]` instead of a
`[RemoveField, AddField]`.
Hi Simon, I like that approach. If it’s not time-sensitive, I’d be happy
to work on a fix and assign the ticket to myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/37006#comment:3>
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/0107019d2b25f0a2-e80c0637-03ae-4a47-a393-b968604e131c-000000%40eu-central-1.amazonses.com.
