Ben Morris wrote:
> Potentially we could have around fifty client applications all attempting
> simultaneous writes
> to a SQLite database stored on a file server.
In that case, I would say quoting directly from the SqLite web page we've
mentioned already should be sufficient to scare management
Thank you for the responses all, and please accept my apologies; I have
obviously not achieved my intended level of clarity in the scenario
description I provided.
Firstly, by multi-user I think the most precise definition would be:
'multiple, concurrent and distributed users'.
The key point that
Richard Hipp wrote:
> Ben Morris wrote:
>> If anyone could share their honest opinions of both my suggested
>> approach, and my colleague's, I would be very grateful.
>
> [snip]
> Using a separate SQLite database on each client to serve as a local cache of
> the master database and then
> period
On 19 Oct 2012, at 8:16am, Ben Morris wrote:
> During Upload, the local database is scanned for rows where the Sync flag
> is true. Each row like this is either updated or inserted into the master
> database (depending on whether a row can be found with the same PK).
>
> During Download, every
On Fri, Oct 19, 2012 at 3:16 AM, Ben Morris wrote:
> Hello all,
>
> I've recently joined an organization that is attempting to use SQLite in a
> multi-user environment (C#, using System.Data.SQLite, layered under the
> DevExpress XPO ORM). Due to the high-latency nature of the networks on
> which
5 matches
Mail list logo
