Re: Autoincrement field rollover

2003-03-07 Thread Alec . Cawley
> The primary key (message_id)is a UNSIGNED BIGINT, > Which is supposed to be 64 bit, with autoincrement. > The each row is deleted as soon as it is fetched > By the client, and also after the expiry of a period > (~30 days). > 64 bits does provide a large number, but there is a > possibility th

Re: Autoincrement field rollover

2003-03-06 Thread Paul DuBois
At 1:19 +0530 3/7/03, Jeethu Rao wrote: Hi, I'm using a mysql table to store small messages in a p2p messaging server. The primary key (message_id)is a UNSIGNED BIGINT, Which is supposed to be 64 bit, with autoincrement. The each row is deleted as soon as it is fetched By the client, and also after

Autoincrement field rollover

2003-03-06 Thread Jeethu Rao
Hi, I'm using a mysql table to store small messages in a p2p messaging server. The primary key (message_id)is a UNSIGNED BIGINT, Which is supposed to be 64 bit, with autoincrement. The each row is deleted as soon as it is fetched By the client, and also after the expiry of a period (~30 days). 64