#33941: AutoField -> BigAutoField causes PostgreSQL sequence value changes
-------------------------------------+-------------------------------------
Reporter: Barry Johnson | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: BigAutoField, | Triage Stage:
sequence | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => fixed
Comment:
Thanks for this ticket, however Django 3.2 is in extended support and
doesn't receive bugfixes anymore (except security patches). Moreover,
Django 4.1+ should not be affected anymore as it uses `IDENTITY` columns
instead of `SERIAL`s and doesn't set sequence values (see
2eea361eff58dd98c409c5227064b901f41bd0d6).
Fixed by 2eea361eff58dd98c409c5227064b901f41bd0d6.
--
Ticket URL: <https://code.djangoproject.com/ticket/33941#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070182d4e48ccb-ab64d76c-a992-4a49-ac00-a3c58deae689-000000%40eu-central-1.amazonses.com.
