On Mon, Jul 14, 2014 at 3:57 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> > The update hook function is an ideal way to do what you're doing. There > is also a pre-update hook: > > <http://www.sqlite.org/sessions/c3ref/preupdate_count.html> > > If you cannot use these, then my instinct is to try to figure out why, > rather than to do something else that cannot possibly be as useful as they > are. > The update hook says "The update hook implementation must not do anything that will modify the database connection that invoked the update hook. Any actions to modify the database connection must be deferred until after the completion of the sqlite3_step() call that triggered the update hook. Note that sqlite3_prepare_v2() and sqlite3_step() both modify their database connections for the meaning of "modify" in this paragraph." Because the update hook only supplies the rowId, I cannot extract the information necessary with this callback. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
