Warren Young wrote: > On 12/5/2013 20:31, Stephen Chrzanowski wrote: [...] >> File handling is NOT SQLites responsibility > > I'm not sure about that. SQLite, at least at one time, was billed as a > competitor for fopen() rather than for Oracle.
But fopen(3) have no locking *at all*. And lower-level locking (flock/fcntl(F_*LCK)) is only advisory - if "rogue application" decide to ignore it, locks won't stop it from changing file. > Maybe all that's needed is a mode where SQLite never creates any > external files. Disable the WAL feature, don't create a lock file, etc. And then there will be question: what if user will open database file in text editor and corrupt it by saving? There are no way you can handle such errors. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
