diff options
| author | Keith Edmiston <kedmist@gmail.com> | 2013-09-07 10:36:31 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-09-07 12:17:01 -0400 |
| commit | 37587624bf79490e97da1bd04547cdce8b77b9fb (patch) | |
| tree | 5fff48880a7905d079037ee11ac9eecb1904867e | |
| parent | afc624cab015be3c05dbe2c184416c4838db4b82 (diff) | |
[1.5.x] Fixed #16992 -- Added InnoDB warning regarding reuse of AUTO_INCREMENT values.
Thanks kent at nsc.liu.se for the report.
Backport of c54fa1a7bc from master
| -rw-r--r-- | docs/ref/databases.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index bf2c084bd7..56844f381c 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -161,7 +161,10 @@ full-text indexing and searching. Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully transactional and supports foreign key references. It's probably the best -choice at this point. +choice at this point. However, note that the the InnoDB autoincrement counter +is lost on a MySQL restart because it does not remember the +``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". This may +result in an inadvertent reuse of :class:`~django.db.models.AutoField` values. If you upgrade an existing project to MySQL 5.5.5 and subsequently add some tables, ensure that your tables are using the same storage engine (i.e. MyISAM |