#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 mtredinnick):
Presumably this is in reference to [http://groups.google.com/group/django-
users/browse_thread/thread/178b03db8014272f this django-users thread].
There was a bit of confusion as to the problem being reported there
initially, but I think I'm happy saying in the end that there isn't really
a bug here, except for a minor documentation/expectation issue.
We say (in the docs) that `AutoField` is an always-incrementing field, but
it could go back and reuse some old numbers, the way we've implemented it
for !SQLite. I'd probably vote for just fixing the docs here, simply
because I prefer maintaining consistency in the SQL we produce, unless
there's a functionality bug.
--
Ticket URL: <http://code.djangoproject.com/ticket/10164#comment:3>
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-updates@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
-~----------~----~----~----~------~----~------~--~---
