Re: identifying rows that have changed

2007-05-30 Thread Perrin Harkins
On 5/30/07, Dan Buettner <[EMAIL PROTECTED]> wrote: #1 - it's not a good approach to "hope" your database keeps up. There are fairly common situations that can come up where you never know how long something will take - unusually high traffic, table check and repair, a bulk load into the same or

Re: identifying rows that have changed

2007-05-30 Thread Dan Buettner
Perrin, I like #3 the best. #1 - it's not a good approach to "hope" your database keeps up. There are fairly common situations that can come up where you never know how long something will take - unusually high traffic, table check and repair, a bulk load into the same or another database on tha

identifying rows that have changed

2007-05-30 Thread Perrin Harkins
Hi, I'm working on a rewrite of a batch process that operates on a large InnoDB database. In the past, it would process the entire database every night, but now the size of the data is making that impossible, and there is a desire for the process to operate in near real-time, so I'm rewriting it