Bug #12098 MySQL Reference Manual: "lock type compatibility matrix" Unclear
Submitted: 21 Jul 2005 22:08 Modified: 21 Aug 2005 22:21
Reporter: Decline Tostate Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:Your Web Site OS:Your Web Site
Assigned to: Bugs System CPU Architecture:Any

[21 Jul 2005 22:08] Decline Tostate 
Description:
On page "http://dev.mysql.com/doc/mysql/en/innodb-lock-modes.html", you give the "lock type compatibility matrix".  The top line and the left column are either the lock that's held already and the lock that is being attempted, but you don't say which is which.  And you don't explain what the hyphen means.

I'm sorry to be submitting this here, but I couldn't find a way to send this to you marked as a bug in the documentation.  My apologies.

How to repeat:
qwer
[21 Jul 2005 22:22] Decline Tostate 
I didn't want to post the note using the "Add your own comment" link, and I looked for half an hour for some way to send the report to you privately.  I finally decided that I had spent enough time looking for it, so I submitted it here.  As you can see, I have no desire for you to let me know (1) whether you're going to ignore me or (2) pass this on to the correct person.  I also have no desire for you to let me know how the matrix should be read.
[22 Jul 2005 0:19] Heikki Tuuri 
Hi!

In lock compatibility, it does not matter in which order the locks are requested by the two users. An X-lock simply is incompatible with an S-lock.

I am assigning this bug report to Jan Lindström. The hyphen apparently means 'no lock'.

Regards,

Heikki
[11 Aug 2005 12:08] Jan Lindström 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

http://lists.mysql.com/internals/28152
[21 Aug 2005 22:21] Mike Hillyer 
Patch is present in refman, closing thsi bug.