As mentioned, only for reads, only one for write. But why not create a server
agent that is responsible for handling multiple connections from clients, and
the server agent can be the single connection to the sqLite database?
Bob S
> On Mar 10, 2022, at 08:34 , Paul Dupuis via use-livecode
>
And finally. https://sqlite.org/wal.html
On Thu, Mar 10, 2022 at 11:55 AM Tom Glod wrote:
> sorry about the double paste. :)
>
> On Thu, Mar 10, 2022 at 11:54 AM Tom Glod wrote:
>
>> For writing its only ever 1, but it can have multiple readers if you use
>> the write ahead log .
>>
>> PRAG
sorry about the double paste. :)
On Thu, Mar 10, 2022 at 11:54 AM Tom Glod wrote:
> For writing its only ever 1, but it can have multiple readers if you use
> the write ahead log .
>
> PRAGMA journal_mode=WAL;
>
> run that when creating database.never tested, but based on documentation.
> n
For writing its only ever 1, but it can have multiple readers if you use
the write ahead log .
PRAGMA journal_mode=WAL;
run that when creating database.never tested, but based on documentation. never
tested, but based on documentation.
let me know if you test it successfully.
On Thu, Mar 10
Can a sqlLite database file on disk be accessed by more than 1 LiveCode
app at the same time?
A server hosted mySql database can be accessed by any number of client
LC apps at the same time as the serve side mySql does the record locking
necessary, but what about a sqlLite file?
Obviously, I
