#10164: AutoField is broken for sqlite backend [patch included]
---------------------------------------------------+------------------------
Reporter: malte | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords: sqlite
autoincrement
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by fwenzel):
This should be included. The patch looks like a good solution for it.
Rationale:
In spots where database IDs are exposed publicly, for example as paths:
/item/1, deleting the latest item and adding a new one will result in the
same ID (and thus, path) being reassigned in SQLite only, and only because
Django is not using the auto_increment feature SQLite provides.
For the sake of consistency between DB backends, I suggest accepting the
patch.
If needed, I could add a test ensuring the PKs Django generates increase
monotonously.
--
Ticket URL: <http://code.djangoproject.com/ticket/10164#comment:4>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
