#35763: Setting the auto increment value of a database model breaks when you
add a
new field to the model
-------------------------------------+-------------------------------------
Reporter: Kevin Renskers | Owner: Sachin
| Kundalwal
Type: Bug | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Kevin, I think that if you could create a failing test in the Django's own
test suite, it could help pushing this forward.
Replying to [comment:6 Natalia Bidart]:
> If this would be the case (sequences are lost when columns are added),
then this would be a issue affecting, for example, any primary key,
wouldn't it? We should've had reports long time ago...
I think the issue is not that the sequence itself is lost, but re-creating
the table and the related sequence is resetting the sequence to the next
available value, instead of keeping the manually-set value of the
sequence.
--
Ticket URL: <https://code.djangoproject.com/ticket/35763#comment:9>
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/010701920b905ada-285077e4-78ba-4498-b3d1-9397324bbc97-000000%40eu-central-1.amazonses.com.
