On Wednesday 16 August 2006 12:16, [EMAIL PROTECTED] wrote:
> "Christian Nassau" <[EMAIL PROTECTED]> wrote:
> > I would guess that your requests acquire (shared) read locks when the
> > transaction starts and then fail/deadlock when they try to upgrade this
> > to a write lock in your insert/update statement. Maybe it would help to
> > start the transactions with "BEGIN IMMEDIATE" or "BEGIN EXCLUSIVE"...?
>
> In TCL, you can do this as:
>
> db transaction immediate {
> # code here
> }
>
> --
> D. Richard Hipp <[EMAIL PROTECTED]>
>
>
> ---------------------------------------------------------------------------
>-- To unsubscribe, send email to [EMAIL PROTECTED]
> ---------------------------------------------------------------------------
>--
Hi Christian, Richard,
I thought about that, but I didn't want to include
the selects into the locked phase, keeping lock
times as short as possible. Shouldn't it work
correctly with a deferred lock?
Nevertheless, I'll give it a try.
Thanks for your help and special thanks to
Richard for sqlite
Ulrich
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
