On Mon, Jan 27, 2014 at 2:13 PM, Tom Lockhart <tlockhart1...@gmail.com> wrote: > MySQL started as a non-ACID query server (not a full relational database in > the accepted sense) and these kinds of issues likely stem from that history. > Folks getting started with databases and django may want to consider using > Postgres for their foundation.
it's true that MySQL started as a very limited project and grew from there, meaning that there are still several shortcomings when compared with more complete and robust implementations, like Postgresql. but this specific issue, isn't because of that history. in fact, the old MyISAM storage engine handles it differently: autoincrement fields are monotonically incrementing. (unless the storage gets corrupted). it's the InnoDB implementation the one that didn't bother to handle full monotonicity, considering the uniqueness and incrementing conditions enough. AFAIR, the SQL standard doesn't require full monotonicity... does it even define autoincrement fields? if there's no hard standard, i don't think it could be considered a bug. -- Javier -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/CAFkDaoQNwnC-3Ka3X1SS6%2Bk-%3DfMaxmj0DEKgV3QmMf4vkQQOyw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
