> I'd also love any suggestions/criticisms of the above architecture. I'm
> trying to address what is a potentially significant performance issue for
us
> (we hope to allow the main table to grow to tens to hundreds of millions
of
> rows before pruning it down), but there might be a much simpler way to
> approach the problem. Experiences implementing solutions to similar
problems
> would be much appreciated.
Isn't this a case for user variables? Set a user variable to now() at the
start if the insert, then use that rather than now() in the insert?
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
