This probably isn't much better than coupling the reader/writer, but you could have the reader periodically query a table that keeps track of the last update.
Every time the writer makes a change to the database have it write to another one row by one column table. That table would just contain a serial number that changes (increases) every time the database is updated. This way, the reader would just have to compare the new serial to the last one it got, and if it's different do whatever it is the reader does. Again, this doesn't help you with a "table changed" event, but it may serve your needs. -Micah Caldwell >-----Original Message----- >From: [email protected] >Sent: 04/19/05 - 00:53 >To: [email protected] >Subject: RE: [sqlite] Callback when table contents have changed > >I've asked this two weeks ago but no reply yet... > >I've got one application that writes to the database, and one that >reads >from it. When a table in the database has changed, the reading >application needs to know that. Of course I can send a signal from the > >writer to the reader app, but if the database would have a means for >that, >I think it would be more elegant (not directly coupling the writer and >the >reader). So it would be nice if a C application could subscribe to >"table >changed" events. I don't think it is currently possible with >SQLite, is >it? > >Frank
