Fixed 16992 -- Added InnoDB warning regarding reuse of AUTO_INCREMENT values.

Thanks kent at nsc.liu.se for the report.
This commit is contained in:
Keith Edmiston 2013-09-07 10:36:31 -05:00 committed by Tim Graham
parent bacbbb481d
commit c54fa1a7bc
1 changed files with 4 additions and 1 deletions

View File

@ -214,7 +214,10 @@ full-text indexing and searching.
Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully 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 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 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 tables, ensure that your tables are using the same storage engine (i.e. MyISAM