Okay, thanks. That sounds workable. Am I right to understand from the documentation that I have to create three triggers (insert, update, and delete) for each table concerned?
Thanks again, John On 22/02/2008, Samuel Neff <[EMAIL PROTECTED]> wrote: > Use triggers to populate some table such as Changes or History or > LatestChange or something. Then you can just query this one table for > updates. > > HTH, > > Sam > > > > On Fri, Feb 22, 2008 at 4:28 PM, John Karp <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > I'm using SQLite to maintain a database that is used by several > > independent processes. One process is a 'viewer', and it is important > > that it always be presenting the latest data. Currently, I am using > > Linux's inotify feature to detect any changes to the file. This works > > fairly well, except it has no way of knowing which particular tables > > have changed. Is there some internal table-level timestamp or > > versioning that I could access? > > > > Or will I need to create an auxiliary table that contains table > > timestamps? Is there another, more elegant possibility I'm not > > thinking of? > > > > Thanks in advance, > > John > > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@sqlite.org > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
