2011/6/30 Simon Slavin <slav...@bigfraud.org> > > As long as the application is > > running, I want to be sure that nobody writes to the database. > > This may be sensible if the application never waits for any input. Some > sort of bulk-update application, for example, or an overnight batch run. > But if the application pauses for input, aren't you giving a user power > over the database ? They could just start up the application then leave it > in the background while they browse the web. >
It is a single user application and database. So I do not think it is a problem. With a multi-user application I would not do this, and check that the data has not changed before doing an update. -- Cecil Westerhof _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
