Robert A. Rosenberg wrote:
At 13:37 -0400 on 06/19/2004, Michael Stassen wrote about Re: AUTO_INCREMENT problem... ER_DUP_ENTRY? (No, it's not a:
Finally, just to cover all the bases, that really is 87 million inserts, not
8.7 million, right? I only ask because a MEDIUMINT column runs out a little
past 8.3 million.
It goes to 16+ Million if you say UNSIGNED. Why lose half the range by allowing the negative numbers that will never be used?
You missed my point. I was not recommending using MEDIUMINT as an auto_increment id, I was attempting to help Kevin figure out why his AUTO_INCREMENT column was giving a duplicate key error. If he was doing an 8.7 million row bulk insert into a table with a MEDIUMINT AUTO_INCREMENT id, then he would get a duplicate key error near the end. I did not think this was the likely explanation, but I wanted to rule it out. Kevin has already confirmed that that is not the problem. In fact, it seems clear that he's getting a duplicate key error long before hitting max int. So while I agree that doubling the range by making the auto_increment column UNSIGNED is a good idea, I think it's clearly not relevant to the problem at hand.
Michael
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
