Paxdo Presse wrote:
>>> Are we to understand that the pending / exclusive locks function differently
>>> and allow simultaneous shared locks?
>>
>> Yes. Note that, with WAL, writers never write to the same areas of files
>> that readers may read from.
>
> This would mean that with wal mode,
> S
Thank you Simon and Igor.
>> Are we to understand that the pending / exclusive locks function differently
>> and allow simultaneous shared locks?
>
> Yes. Note that, with WAL, writers never write to the same areas of files that
> readers may read from.
This would mean that with wal mode,
Sqlit
Paxdo Presse wrote:
> In the doc, it is indicated that exclusive lock is required to write to the
> database.
> In this case, it can not be simultaneously other locks for reading (Shared..).
>
> And in wal mode?
It can, obviously.
> Are we to understand that the pending / exclusive locks funct
On 16 Dec 2011, at 2:56pm, Paxdo Presse wrote:
> In the doc, it is indicated that exclusive lock is required to write to the
> database.
> In this case, it can not be simultaneously other locks for reading (Shared..).
>
> And in wal mode?
>
> Are we to understand that the pending / exclusive
In the doc, it is indicated that exclusive lock is required to write to the
database.
In this case, it can not be simultaneously other locks for reading (Shared..).
And in wal mode?
Are we to understand that the pending / exclusive locks function differently
and allow simultaneous shared loc
Paxdo Presse wrote:
> With WAL mode,
> there may be multiple readers and one writer, SIMULTANEOUSLY.
>
> is very different from the rollback mode.
>
> Should we handle locks and transactions differently?
How do you handle them now? Is there a particular scenario you are concerned
about?
--
Ig
Hi,
With WAL mode,
there may be multiple readers and one writer, SIMULTANEOUSLY.
is very different from the rollback mode.
Should we handle locks and transactions differently?
Thank you,
olivier
___
sqlite-users mailing list
sqlite-users@sqlite.org
7 matches
Mail list logo