#36358: Tables with composite primary keys including integer columns improperly
get
introspected as AutoField on SQLite
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"ec73fd67466e0e4841d9ecd0f217c02ce842d860" ec73fd67]:
{{{#!CommitTicketReference repository=""
revision="ec73fd67466e0e4841d9ecd0f217c02ce842d860"
[5.2.x] Fixed #36358 -- Corrected introspection of composite primary keys
on SQLite.
Previously, any first field of a composite primary key with type
`INTEGER` was incorrectly introspected as an `AutoField` due to SQLite
treating `INTEGER PRIMARY KEY` as an alias for the `ROWID`.
This change ensures that integer fields in composite PKs are not
mistaken for auto-incrementing fields.
Thanks Jacob Walls and Sarah Boyce for the reviews.
Backport of 07100db6f46255ec6ef70b860495f977473684d6 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36358#comment:5>
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/0107019686fa7ceb-72d45a5d-d030-4e1e-aab6-783ec6077535-000000%40eu-central-1.amazonses.com.
