#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 Natalia Bidart):
Replying to [comment:4 Kevin Renskers]:
> It really does feel like a Django bug to me though. It only breaks using
SQLite, and only when adding a second migration.
Are you saying that further migrations (third, fourth) are not causing any
issues for you?
> I don't understand how this issue is located "in my custom code". I'm
just updating the auto increment using SQLite's command for that.
What I mean is that your use case seems a very specific need arising from
a niche use case. I don't think this applies to the broader ecosystem, and
Django is a framework designed to offer robust and accurate solutions for
common scenarios.
My advice at this time would be to start a new conversation on the
[https://forum.djangoproject.com/c/internals/5 Django Forum], where you'll
reach a wider audience and likely get extra feedback.
--
Ticket URL: <https://code.djangoproject.com/ticket/35763#comment:7>
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/010701920a485c8b-62acc620-54ac-48fc-b842-ede64dc5bc24-000000%40eu-central-1.amazonses.com.
