> On Mar 25, 2017, at 3:52 PM, petern <peter.nichvolo...@gmail.com> wrote: > > So finally, here is the question. Is there a SQLite API way for reader > connections to block and wait for a meaningful change, like a new row, in > the 'cmd' table instead of madly polling and using up database concurrency > resources? [Block with timeout would be even more desirable of course.]
No; I’ve asked about this myself. Alternatives to polling are either (a) using a platform-specific filesystem notification API to inform you when the database file(s) have been changed; or (b) using a platform-specific cross-process notification API to let the writer process signal that there are new changes. If you only want to know about specific types of changes, then option (b) sounds best. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
