One method you can use to see changes is to hook up triggers on update/insert. Since you can add functions to be called from SQL, you just have to add whatever IPC system you desire as an SQLite function (see sqlite_create_function). This function can then be invoked through your triggers, and away you go!
Frosstoise. On Fri, Mar 20, 2009 at 10:22 PM, Ricky Huang <[email protected]> wrote: > Here's my scenario, I have two applications, reader and a writer, and > a shared database. Writer will be writing changes to the database and > reader will be reading. Originally my idea was for the reader to use > sqlite3_update_hook() to watch for database changes. But after I got > the code written, the hooked function was never called. A little > inter-tubes research revealed this: http://tinyurl.com/dc279r. It > basically says sqlite3_update_hook() is not designed for that. > > My question is, does SQLite offer ways of hooking up a second > application to changes in a shared DB without polling? > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
