2 Mar 2007 14:26
Re: SELECT gets suspended if the table contains a row lock (!)
Robert Klemme <shortcutter <at> googlemail.com>
2007-03-02 13:26:38 GMT
2007-03-02 13:26:38 GMT
2007/2/15, Eduard M <vef206 <at> gmail.com>: > Hi, > I experience the following scenario: > 1. update a row in a table (say, in one SQLStudio session, without doing > commit). > 2. In another session (SQLStudio or whatever), try to select * from this > table. Or try to select the row that is being updated. SELECT does not > return until the other session is committed. > > Is this a feature of Maxdb or it can be controlled by some database > parameter? http://dev.mysql.com/doc/maxdb/en/a9/5727401544ed01e10000000a155106/content.htm http://dev.mysql.com/doc/maxdb/en/c4/812640632cec01e10000000a155106/content.htm robert -- Have a look: http://www.flickr.com/photos/fussel-foto/ -- -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/maxdb?unsub=gcdm-maxdb <at> m.gmane.org
RSS Feed