Re: MySQL ID -- what happens when you run out of range?

On Mon, Jan 25, 2010 at 10:00 PM, Michael A. Peters <mpeters@mac.com> wrote: > Shawn McKenzie wrote: >> >> Joseph Thayne wrote: >>> >>> That is incorrect.  What will happen is as follows: >>> >>> 1.  The value will be incremented by 1 causing the value to be greater >>> than the maximum integer allowed. >>> 2.  MySQL will see this as a problem and "truncate" it to the closest >>> value. >>> 3.  MySQL will then try and insert the new row with the updated id.. >>> 4.  MySQL will find that the id already exists, and will return a >>> duplicate ID error. >> >> 5. A tear is rendered in the space time continuum! >> > > 6. An alternate version of Dr. Rodney McKay from an alternate universe > appears, and goes by "Rod". > 7. Then you realize that MySQL handles certain things, such as the aforementioned problem, very badly and does not comply to standards and isn't even ACID compliant, so you then switch to PostgreSQL instead.