#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
--------------------------------------+------------------------------------
Reporter: kent@… | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by aaugustin):
* component: Database layer (models, ORM) => Documentation
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
The MySQL devs say:
> This behavior is a documented feature which will be fixed in the future
at the same time a fast COUNT(*) is introduced to InnoDB.
That was in 2003; I'm not holding my breath. And I don't think we have to
document every bug in MySQL.
That said, since it was decided for #10164 to enforce non-reusable primary
keys, in this case, it's worth adding a paragraph to the MySQL notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/16992#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
