On Jan 20, 2006, at 8:25 AM, Will Leshner wrote:
Thanks for this information. It sounds like a reasonable precaution might be not to make "too many" changes to a database in one transaction. But I guess knowing how many changes is too many would be a pretty hard thing to figure out.
Sorry to reply my own email, but I wonder if it might be useful to have some mechanism by which SQLite could report back when it has filled its cache and is about to spill it to disk? I'm not sure what a user would do with such a callback. It's probably unlikely that a commit could occur right at that spot because SQLite itself will be in the middle of doing something else. But maybe the callback could allow the user to abort the writing of the cache, and if that happened, it could be treated as some kind of fatal error that would basically abort the entire transaction.
