db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kasper, Kay" <kay.kas...@ckc.de>
Subject AW: locking problem when selecting data
Date Thu, 07 Jun 2007 15:13:54 GMT
Hi Mark,

thanks for your answer. But why is there already a lock on the row. All
outher statements have been committed or have not selected the row. So there
should be no other lock.

I use the standard row locking of Derby which is, as far as i know,
TRANSACTION_READ_COMMITTED.

Kay

-----Urspr√ľngliche Nachricht-----
Von: Mark Thornton [mailto:mthornton@optrak.co.uk]
Gesendet: Donnerstag, 7. Juni 2007 17:10
An: Derby Discussion
Betreff: Re: locking problem when selecting data


Kasper, Kay wrote:
> On other databases like Orcale and hqsl i don't have that problem. Whats
> wrong with the row locking? Why does a normal select try to set a lock?
>   
Unless your transaction isolation is TRANSACTION_READ_UNCOMMITTED, I 
think a row (or table) lock is required for any select.

Mark Thornton


--------------------------
ckc ag
Sitz:
Industriestr. 10
38110 Braunschweig

Telefon 05307 / 80 20 0
Telefax 05307 / 80 20 444
http://www.ckc.de

Amtsgericht Braunschweig
HRB 5405

Vorstand:
H.-G. Christian Krentel
(Vorsitzender)

Aufsichtsrat:
Dr. Heinz-Werner Weinrich
(Vorsitzender)
Hans Bodenstein
Dr. Rita Schulz
--------------------------


Mime
View raw message