andychambers2002-/E1597aS9LT10XsdtD+oqA@xxxxxxxxxxxxxxxx wrote:
>>
>> An error is thrown immediately if a deadlock situation is detected by
>> SQLite. If that's not what happened, can you post your test scripts?
>
> I think that must be what happened. I was locking the database by
> opening a transaction in a sqlite session like so...
>
> $ sqlite
>> begin
>> insert into readings (1, 1);
Hello, amazing how easy a deadlock situation can occur. Two users
issuing above statements is enough. Can anybody tell it this is a
problem in track and, if so, how it is handled?
I guess the duration of a transaction will not be longer then the
handling of a single http request.
Does it use the default isolation_level?
Is the error handled programattically?
Thanks in advance, Edzard
|
