I read this on the django project site: > > Since MySQL 5.5.5, the default storage engine is > InnoDB<http://dev.mysql.com/doc/refman/5.5/en/innodb-storage-engine.html>. > This engine is fully transactional and supports foreign key references. > It’s probably the best 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 > AutoField<https://docs.djangoproject.com/en/1.6/ref/models/fields/#django.db.models.AutoField> > values.
Now to my newby senses, this is a huge problem. How can you have a primary key, or a foreign key, without the assurance that they are unique? But I did some searching around the net, and while there are some suggested fixes here and there, no one seems to be in a panic about this. So, my question is, why? Are unique primary keys not as important as I thought they were? How are you dealing with this, if you use mysql/innodb? Is this a reason to jump to nosql? Help me wrap my brain around this. Thanks. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ac13c90b-bed2-488b-b145-3a7cde034b3a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
