Is this a Bug or not?
--------------53E593AD4920FCA74D5D7E96
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Problem Scenario:
Through one dbaccess session I tried to insert a record into a table
after giving "Begin work" ( Note: I didnot commit or Rollback )
Through another dbaccess session I tried to insert the same record into
the same table - I got an error that primary key constraint is
violated and I also got the ISAM error.
Now if I rolled back the previous "work" - neither of my record made it
to the database. ( This seems OK - but I have my own reservation as to
the second session should have been locked till the first one is
released )
Now I wanted to test this scenario and I gave the following command in
the second dbaccess session before trying to insert the record
" set lock mode to wait "
Still in the second session my insert command was not waiting for the
lock to be released ( by the first session ), but went ahead and tried
to insert the record and came back with the same error.
Is this normal behavior or does other RDBMS behave differently .
Response will be appreciated
-Suresh
--------------53E593AD4920FCA74D5D7E96
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<HTML>
Problem Scenario:
<P>Through one dbaccess session I tried to insert a record into a table
after giving "Begin work" ( Note: I didnot commit or
Rollback )
<P>Through another dbaccess session I tried to insert the <U>same record
into the same table</U> - I got an error that primary key constraint
is violated and I also got the ISAM error.
<P>Now if I rolled back the previous "work" - neither of my record
made it to the database. ( This seems OK - but I have my own reservation
as to the second session should have been locked till the first one is
released )
<BR>
<P>Now I wanted to test this scenario and I gave the following command
in the second dbaccess session before trying to insert the record
<BR>" set lock mode to wait "
<P>Still in the second session my insert command was not waiting
for the lock to be released ( by the first session ), but went ahead and
tried to insert the record and came back with the same error.
<P>Is this normal behavior or does other RDBMS behave differently .
<P>Response will be appreciated
<P>-Suresh
<BR> </HTML>
--------------53E593AD4920FCA74D5D7E96--