--- Begin Message ---
Hi all,
I've got a strange lock when trying to modify data in a table from two
simultaneous sessions.
I did following:
1) Connect to database from sqlcli (let it be first session)
[EMAIL PROTECTED]:~$ sqlcli-wrapper -d testdb -u dba,dba
Welcome to the SAP DB interactive terminal.
Type: \h for help with commands
\q to quit
2)Create test table
create table testlock (id integer)
0 rows affected (24 msec)
3)Set autocommit off
sqlcli testdb=> \a
Autocommit mode switched OFF
4)Then started another session (let it be second) and set autocommit false
5)Inserted into testlock table a row from first session
sqlcli testdb=> insert into testlock values(1)
1 row affected (1 msec)
6)Inserted int testlock table a row from second session
sqlcli testdb=> insert into testlock values(2)
1 row affected (1 msec)
7) Selecting all from testlock table from first session
sqlcli testdb=> select * from testlock
And I got nothing.... It seems that table is locked and we can't do
anything.
If in this moment we commit second session we get everything:
sqlcli testdb=> select * from testlock
| ID |
| -------------- |
| 1 |
| 2 |
2 rows selected (2 msec)
Transaction isolation level is set by default to read_commited.
Information about kernel and db_instance:
dbmcli on testdb>version
OK
version,os,dbroot,logon,code,swap
"7.5.0","UNIX","/usr/lib/maxdb/7.5.00",True,ASCII,2
Could you explain this situation?
To my best knoledge we should recieve data from first session i.e. value
1. Am I wrong?
Alexander Tsirel
--- End Message ---
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
