> > If you _need_ exclusiveaccess all along, then start app, "begin > > exclusive", do your stuf, "commit" and exit. > > > >The 'problem' is that the application can run for the whole day.
Granted. And the 'problem' is ??? > > What I don't get is you later say it's a single-user, single-app > > use. You don't have to take that much care in this case. > >In principal could the user use another program to change the >database. But >maybe I am paranoid. ;-} One sometimes has to. If you admin the system, then place the DB in a folder owned by a special account and deny user access. Run your app under this account and the system will prevent unexpected writes from outside. -- <mailto:j...@q-e-d.org>j...@antichoc.net _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
