Re: failure of auto increment in inndb (mysql)

2014-01-27 Thread Erik Cederstrand
Den 27/01/2014 kl. 20.13 skrev Tom Lockhart : >> ... >> Now Jane Smith has the same ID as John Doe had previously. This may not be a >> problem in your situation, or it might. Anyway it's good practice to never >> re-purpose an ID. > > MySQL started as a non-ACID query server (not a full relati

Re: failure of auto increment in inndb (mysql)

2014-01-27 Thread Javier Guerra Giraldez
On Mon, Jan 27, 2014 at 2:13 PM, Tom Lockhart 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 > Postgr

Re: failure of auto increment in inndb (mysql)

2014-01-27 Thread Tom Lockhart
> ... > Now Jane Smith has the same ID as John Doe had previously. This may not be a > problem in your situation, or it might. Anyway it's good practice to never > re-purpose an ID. MySQL started as a non-ACID query server (not a full relational database in the accepted sense) and these kinds o

Re: failure of auto increment in inndb (mysql)

2014-01-27 Thread Erik Cederstrand
Den 27/01/2014 kl. 17.22 skrev Malik Rumi : > I read this on the django project site: > 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 > choice at this point. However, note that the the In