diff options
| author | Simon Charette <charette.s@gmail.com> | 2025-04-28 23:35:04 -0400 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-04-30 10:51:48 -0300 |
| commit | 07100db6f46255ec6ef70b860495f977473684d6 (patch) | |
| tree | 74b23bbbd9062779951bc195afadb9602a06d34a /docs | |
| parent | 4c75858135589f3a00e32eb4d476074536371a32 (diff) | |
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.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/5.2.1.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/releases/5.2.1.txt b/docs/releases/5.2.1.txt index 19d14bbddf..8ec4d58a92 100644 --- a/docs/releases/5.2.1.txt +++ b/docs/releases/5.2.1.txt @@ -55,3 +55,7 @@ Bugfixes * Fixed a regression in Django 5.2 that caused a crash when using ``update()`` on a ``QuerySet`` filtered against a related model and including references to annotations through ``values()`` (:ticket:`36360`). + +* Fixed a bug in composite primary key introspection that caused + ``IntegerField`` to be wrongly identified as ``AutoField`` on SQLite + (:ticket:`36358`). |