You definitely don't want to use timestamping for unique IDs. You want to use an auto-incrementing column or similar. See
http://www.mysql.com/doc/en/example-AUTO_INCREMENT.html ____________________________________________________________ Eamon Daly NextWave Media Group LLC Tel: 1 773 975-1115 Fax: 1 773 913-0970 ----- Original Message ----- From: "Craig Jackson" <[EMAIL PROTECTED]> To: "mysql" <[EMAIL PROTECTED]> Sent: Thursday, February 12, 2004 11:30 AM Subject: Unique IDs > Hello People, > > This is my first post to this list. I am having a bit of a problem that > Google doesn't seem to help with, and I'm not sure what part of Mysql > docs will help. > > I have a very large web app that uses timestamp for unique IDs. > Everything was rolling fine until we started getting many users per > second, causing some of the unique IDs to not be unique -- users were > being assigned the same timestamp. Since the web app is so large we > don't want to change the method of assigning IDs as it would create a > major project. > > I have looked at Locking and Insert Delay, but I'm not sure that will > help. > > Does anyone have a suggestion? We are using 4.0.14 and ISAM tables and > PHP 4.3. > > Thanks, > Craig Jackson > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]