#33919: Primary keys added in non-initial migration are not created as identity
columns in PostgreSQL
-------------------------------------+-------------------------------------
Reporter: jackcbrown89 | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: postgres | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"3848475eeb5ee8f7729440f50c04fd85cf8bea66" 3848475e]:
{{{
#!CommitTicketReference repository=""
revision="3848475eeb5ee8f7729440f50c04fd85cf8bea66"
[4.1.x] Fixed #33919 -- Fixed adding AutoFields on PostgreSQL.
Thanks Jack Calvin Brown for the report.
Regression in 2eea361eff58dd98c409c5227064b901f41bd0d6.
Backport of 5c803bc0702511c8bc05e9db600367a465514f82 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33919#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018292af50a5-541914fe-3c44-4333-85c9-606437477c9a-000000%40eu-central-1.amazonses.com.
