Flavio Silveira wrote : > >When I write a procedure, I have to explicity COMMIT or the >procedure do this automaticaly? I have a problem: I have a >cursor and, for each fetch, i insert some values in a table. >But the table "lock" every time. If I explicity a COMMIT, the >table unlock? > >Thanks and sorry for the bad English :) > I assume, the lock occurs on table into which the rows are inserted ? This may have two reasons : 1. You are running with a high isolation level (3) 2. You are inserting many rows which causes a lock escalation, i.e. many row exclusive locks become one table exclusive lock. You may delay this escalation by increasing the parameter MAXLOCKS.
A transaction end (COMMIT or ROLLBACK) is the only way to get rid of the locks. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
