"Yes, MaxDB keeps some row locks on SELECTs (these 'row_share' locks you may see in
LOCKSTATISTICS) if the isolation level requires it. Simply speaking, if you want a 'read committed' isolation, you must prevent another session from updating a row if you have accesssed it, cause you might want
to read it again (this is an over-simplification)."
Is it possible to have more infos on the behaviour ?
Thanks
Philippe
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
