row-level locking with Pear Database & MySQL

[Wayne Smallman]

OK, anyone have some advice on implementing the likes of SELECT ... FOR
UPDATE / SELECT ... LOCK IN SHARE MODE?

I'm trying to get it working in conjunction with the transaction
facilities built into Pear DB.

Obvious answer to obvious question: yes, I'm using InnoDB-formatted
tables within MySQL.

So far, all of the stuff I've put in place certainly isn't stopping me
from INSERTing, UPDAT[E]ing, but it doesn't seem to be locking the rows
down.

I've created a transaction class with all of the nice autoExecute() and
executeMultiple() methods to make things ultra easy. Which,
incidentally, are all working fine.

So, for example: I open up record ID: 15 in browser A and the same
record in another browser B.

I can then make changes in browser B before COMMIT[t]ing my changes in
browser A.

Obviously, this isn't supposed to happen.

Any help would be great...
--
wayne smallman ][ octane interactive