ROW SHARE/SELECT ... FOR UPDATE + foreign keys

What would people think of adding a note to the ROW SHARE section of Table-Level Locks remarking on the fact that referential integrity checks expressed through foreign keys do SELECT ... FOR UPDATES.

It was somewhat challenging today to try to track down a pervasive locking issue related to a table not directly referenced in a stored procedure but that was referenced by a key in a table that was being updated.

I'm not sure how this changes with the new shared row locking implementation in 8.1...