#10164: AutoField is broken for sqlite backend [patch included]
-------------------------------------+-------------------------------------
Reporter: malte | Owner: nobody
Status: new | Milestone: 1.4
Component: Database | Version: 1.2
layer (models, ORM) | Keywords: sqlite autoincrement
Resolution: | Has patch: 1
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 |
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------
Changes (by lukeplant):
* needs_better_patch: 0 => 1
* stage: Design decision needed => Accepted
Comment:
Replying to [comment:15 johnsmith]:
> 2 years seems like a long time for this nobrainer to be outstanding.
We need compelling reasons to change something like this, because it is
entirely possible that someone is depending on the existing behaviour in
production i.e. people using SQLite for production. So just getting
consistency for the sake of people using SQLite for testing only isn't in
itself the most important consideration.
And we certainly didn't have a compelling reason for the change 2 years
ago. I think we do now though, and no-one has responded otherwise, so I'm
going to accept. If Jacob or Malcolm are still unsure, we probably need to
have a discussion on django-devs.
The patch needs some work to be updated for trunk. Also, if there is a
nice way to do it other than adding an ad-hoc feature addition to the DB
backend that is needed by just this exception, that would be good.
We also need tests, either by testing the SQL generated, or by a
functional test that ensures that IDs are not re-used.
--
Ticket URL: <http://code.djangoproject.com/ticket/10164#comment:16>
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.
