every month or so someone seems to write in with 'database locked' questions. is there any good reason a pragma could not be added to
lock the file in a blocking fashion (pragma locks_block)
lock the whole file vs. byte range locking (pragma allbytes)
??
i realize this yields lower performance - but surely this is not always the case: polling to db to catch it in an unlocked state cannot be a nice for heavy concurrent use as letting the process go to sleep untill notified by the os that a lock has been granted. locking the whole file would be an option for the truely paranoid (like me) who are also doing crazy things like concurrent access of nfs mounted sqlite files. the thought of byte range locks/writes on an nfs mounted file makes me cringe.
regards.
-a -- =============================================================================== | EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov | PHONE :: 303.497.6469 | When you do something, you should burn yourself completely, like a good | bonfire, leaving no trace of yourself. --Shunryu Suzuki ===============================================================================
