The long and short of it is that SQLite uses the os File-Locking APIs
for concurrency.  Network File systems vary wildly in the reliability
of their implementations of these APIs.  If you already have a server
application why not simply force all database access through that?

On Thu, Sep 25, 2008 at 12:04 PM, Gerry Snyder <[EMAIL PROTECTED]> wrote:
> Darrell Lee wrote:
>> Here is my situation: the maximum number of clients that would be
>> reading the SQLite database is 6, of that 6 the maximum number of
>> clients that might be trying to write to the SQLite db is 3.   In you
>> guys experience,  on a scale of 1-10 , 10 being the most likely to
>> happen, what are the chances of the database becoming corrupt if it is
>> on a network share?
>> Thanks,
> If your data are critical isn't a 1 unacceptable? And if not, isn't 10 okay?
> _______________________________________________
> sqlite-users mailing list
sqlite-users mailing list

Reply via email to