Skip to content

Commit

Permalink
[1.6.x] Fixed #16992 -- Added InnoDB warning regarding reuse of AUTO_…
Browse files Browse the repository at this point in the history
…INCREMENT values.

Thanks kent at nsc.liu.se for the report.

Backport of c54fa1a from master
  • Loading branch information
kedmiston authored and timgraham committed Sep 7, 2013
1 parent fac5735 commit a357c85
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/ref/databases.txt
Original file line number Original file line Diff line number Diff line change
Expand Up @@ -218,7 +218,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
Expand Down

0 comments on commit a357c85

Please sign in to comment.