> 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 that it won't be enough.
> My question is, does the autoincrement count rollover
> To zero normally, or will the rollover cause an error?
> Or is there a better way to tackle the problem ?
You must have a *lot* of data to store. My quick calculation says that if
you create a new row every microsecond - which I would think is all you
could expect even of the excellent MySQL - you have enough capacity for
over 200,000 years with BIGINT.
To solve your problem, invest $1 at compound interest today. After 100,000
years, you will have enough money to pay the MySQL team to implement a
SUPERINT of 128 bits - and they will still have 100,000 years to do it.
Then a simple ALTER TABLE command will ensure that your database will last
longer than the Universe.
Alec
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
