From c54fa1a7bc365fec79d4971bf22d5ad2799fde67 Mon Sep 17 00:00:00 2001 From: Keith Edmiston Date: Sat, 7 Sep 2013 10:36:31 -0500 Subject: [PATCH] Fixed 16992 -- Added InnoDB warning regarding reuse of AUTO_INCREMENT values. Thanks kent at nsc.liu.se for the report. --- docs/ref/databases.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index a4e6724c46..75e2d085e8 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -214,7 +214,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