List:MaxDB« Previous MessageNext Message »
From:Matthias Schweizer Date:May 13 2004 1:07pm
Subject:INSERT blocks SELECTs when using isloation level > 0
View as plain text  
Hi,

we are using 7.5.0.11.

We set autocommit off. With all isolation levels > 0 in our installation INSERT to
table T1 locks all "SELECT * FROM T1" until commit or rollback.

This means, we can not display a list of all entries in T1 while someone else inserts a
new entry but has not committed the work.

We expect to get all committed rows from the select.

Switching to isolation level 0 is not a solution (we get uncommitted data).

Can we somehow change this behavior?


We currently check, if we can port an application from oracle to MaxDB.


Matthias Schweizer
SoliDat GmbH



Thread
INSERT blocks SELECTs when using isloation level > 0Matthias Schweizer13 May
RE: INSERT blocks SELECTs when using isloation level > 0Holger Becker13 May
  • Re: INSERT blocks SELECTs when using isloation level > 0Matthias Schweizer13 May
RE: INSERT blocks SELECTs when using isloation level > 0Holger Becker13 May