On Tue, Mar 11, 2008 at 1:30 PM, Neville Franks <[EMAIL PROTECTED]> wrote: > Wednesday, March 12, 2008, 3:50:46 AM, you wrote: > SH> On Mon, Mar 10, 2008 at 6:15 PM, Neville Franks <[EMAIL PROTECTED]> > wrote: > >> I'm displaying tree's which are built from SQL queries and I ideally > >> want the tree control to reflect updates to the underlying tables > >> without have to do queries all over again and rebuild the trees from > >> scratch. > > SH> You need to ponder your model a bit longer. Unless you build it > SH> yourself, there exists no thread of control which would allow SQLite > SH> to monitor the table for changes and notify you if any happen! > SH> Instead, _you_ need to handle this kind of synchronization issue. > > I've not used Triggers, but would have thought they could be very > helpful in reflecting table changes in our application views of same.
Triggers can make changes to the database, but, again, there is no thread of control you can rely on. There is no server coordinating things. Each thread of control runs triggers when it does updates, which means that if some other connection makes a change, that connection runs the triggers, and your connection does not, so your connection will not get an asynchronous notification of the changes. YOU have to provide that kind of asynchronous stuff. -scott _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
