Richard, Ryan,
Thanks for this. We were dimly aware of WAL but until now hadn’t
needed to use it.
We’ve done a quick check with it and it *seems* to work on a test
database. We’ve all read the docs again and paid attention to
https://www.sqlite.org/wal.html#bigwal
To test if it works we st
On Sat, Aug 6, 2016 at 2:09 AM, Dan Kennedy wrote:
> On 08/06/2016 09:52 AM, Kevin O'Gorman wrote:
>
>> On Fri, Aug 5, 2016 at 2:03 PM, Dan Kennedy
>> wrote:
>>
>> On 08/06/2016 03:28 AM, Kevin O'Gorman wrote:
>>>
>>> On Fri, Aug 5, 2016 at 1:08 PM, David Raymond
wrote:
..
>>
On 2016/08/06 10:50 PM, Rob Willett wrote:
Our understanding of this is that many processes can READ the database
at the same time but NO process can INSERT/UPDATE if another is
reading. We had thought that one process can write and multiple
processes can read. Our reading (no pun intended)
On 6 Aug 2016, at 9:53am, Michele Pradella wrote:
> Ok understand... so the question is: if I have just 1 process with 2
> threads reading/writing a network DB, is it safe if threads write at the
> same time? can SQLITE_THREADSAFE [1] define with correct value help
> handle this?
Keith Medcalf
On 8/6/16, Rob Willett wrote:
>
> What we have now found is that when we are running the analytics query
> in one Perl process, we can no longer UPDATE the main database through
> another Perl process. We are getting “database is locked” errors.
Doing "PRAGMA journal_mode=WAL;" on your database (
Hi,
We’ve been using Sqlite though Perl for some time now and have started
to get more adventurous.
Our SQLite database is around 32GB in size, is created and manipulated
by a single Perl process and is working well.
What we now want to do is mine the database using a very long running
que
On 08/06/2016 09:52 AM, Kevin O'Gorman wrote:
On Fri, Aug 5, 2016 at 2:03 PM, Dan Kennedy wrote:
On 08/06/2016 03:28 AM, Kevin O'Gorman wrote:
On Fri, Aug 5, 2016 at 1:08 PM, David Raymond
wrote:
..
Apart from the default location of the files, it reads like your next main
concern is
Ok understand... so the question is: if I have just 1 process with 2
threads reading/writing a network DB, is it safe if threads write at the
same time? can SQLITE_THREADSAFE [1] define with correct value help
handle this?
Il 2016-08-05 14:52 Keith Medcalf ha scritto:
> iSCSI is not shared net
8 matches
Mail list logo