id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 16992,MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart),kent@…,Keith Edmiston,"I recently ran into problems with Django's automatic id field. When the latest added object in a table was deleted, a new object created some time later reused the same id value as the deleted object. It turned out that this was due to the fact that I had restarted the MySQL server between the deletion and the creation, and the fact that the InnoDB backend does not remember the AUTO_INCREMENT value when restarted (instead recreating it as ""max(id)+1""). See for example http://bugs.mysql.com/bug.php?id=727 I guess there is not much that Django can do to fix this, but I think the MySQL/InnoDB documentation should mention this peculiarity. ",Cleanup/optimization,closed,Documentation,1.3,Normal,fixed,,,Accepted,0,0,0,0,1,0