If I have two transactions and one of them is updating a set of rows and the second one is updating a different set of rows, the second transaction is forced to wait. I have an unique index on two columns of the table. I found that there is a bug associated with this problem which will be fixed later (Q3 of 2004):
http://bugs.mysql.com/bug.php?id=3300


But I need a workaround immediately! Can anyone answer the following questions:

- How can I figure out what are all the rows getting locked by a query? If I know this I can rewrite my query to lock fewer rows.

- How can I create an index and write my queries so that only those rows that need to be updated get locked? I have tried many combinations of indexes and queries in a simple test case but have not been successful.

- Does the order of indexes in a concatenated index matter? From my simple tests it does not appear so.

I will really appreciate any help,

Sunondo



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to