On 5/18/05, Gerhard Haering <[EMAIL PROTECTED]> wrote: > On Wed, May 18, 2005 at 10:22:39AM -0500, Mike Owens wrote: > > What about sqlite3_set_authorizer()? Implement a callback function and > > monitor changes in transaction state for each connection object: [...] > > Didn't try, yet. But does this get called for ON COMMIT ROLLBACK, too?
You mean ON CONFLICT ROLLBACK right? I haven't tried it but I would be willing to wager it does by arguing that a rollback is in fact a change in transaction state. > Also, it's a bit awkward to have to use an authorizer just for this > purpose. It's just a simple hook that you set on your connection object's open()/connect() function. It's no different than processing queries in the 2.x days. I only suggested it because technically it seemed to be an API call which can do what you were looking for. But I confess that I typically use authorizer for other things in addition to monitoring transactions, such as watching for schema changes. -- Mike
