Thanks again Simon,
I am actually asking for queries that may well not be in an EXCLUSIVE
section, but I've realised that I can simulate the blocking in my own
application by busy-waiting.
Ian
On 12/06/2011 15:16, Simon Slavin wrote:
> On 12 Jun 2011, at 3:05pm, Ian Hardingham wrote:
>
>> If p
On 12 Jun 2011, at 3:05pm, Ian Hardingham wrote:
> If process B tries to access a table which process A is currently
> writing to, is an error returned or does sqlite block? I very much need
> SQLite to block - is there an option for that?
[context: Ian is explicitly using BEGIN EXCLUSIVE for
A further question to this.
If process B tries to access a table which process A is currently
writing to, is an error returned or does sqlite block? I very much need
SQLite to block - is there an option for that?
Thanks,
Ian
On 12/06/2011 12:23, Simon Slavin wrote:
> On 12 Jun 2011, at 12:07p
Hey Simon, thanks for this.
I would really like to only block specifically one operation, rather
than not allowing any database access in the exclusive block - is this
possible?
Thanks,
Ian
> I'm not certain I understand your question but SQLite performs a kind of
> mutexing by default. If y
On 12 Jun 2011, at 12:07pm, Ian Hardingham wrote:
> I believe it's fine to have four applications open the same database
> file and use it concurrently.
Assuming you are compiling without any special directives which turn this
ability off. For instance, read about everything mentioned in the
5 matches
Mail list logo