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:16:43 -0400 |
| commit | a357c854c91b513e3713f2eb72e9742d49c2e701 (patch) | |
| tree | 46349fa5f2fe6e1195e56b3189028d7bb353929d | |
| parent | fac5735a3daffb82b67ff489f0c963eaf953f6e7 (diff) | |
| download | django-a357c854c91b513e3713f2eb72e9742d49c2e701.tar.gz | |
[1.6.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 ff88c24386..b1b9bc0eed 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -218,7 +218,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 |