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
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
[EMAIL PROTECTED] wrote:
> I would like to use SQLite from a network share. I would like to create a
> server app that would do all of the writing to the database except for
> certain tables, one table per client,the clients would write to their own
> table only. The client drops it's
> Another question I have is do I understand correctly that an SQLite
> database, on a network share, has no problems with many readers, the
> problem starts with many writers. Is this correct?
>
> Thanks,
> TD
Yes, you'll have problems with many writers since each network file
system
On Mon, Sep 15, 2008 at 11:49:48PM -0400, [EMAIL PROTECTED] scratched on the
wall:
> I would like to use SQLite from a network share. I would like to create a
> server app that would do all of the writing to the database except for
> certain tables, one table per client,the clients would write
5 matches
Mail list logo
