Thanks for the feedback Calzone and Mika. The situation I am thinking of is like code control. "Check out" the object to work on, and while it is checked out you can be certain that there won't be conflicting edits.
Looks like there is a long climb ahead here. Regards, Langdon calzone wrote: > Are you looking to lock the record for more than just an instant in > time? Do you mean you need to protect records as if you were checking > out code until the user checks it back in (for instance a person is > editing the contents of an article that someone else would otherwise > also have permission to edit)? > > If so, then an approach like Mika is suggesting is definitely what you > will need. > > On the other hand, if all you are concerned about is the potential for > a race condition during an update (for instance updating a running > balance in the table by reading and incrementing the existing balance), > you should go ahead and use mysql's table locking. > > http://dev.mysql.com/doc/refman/4.1/en/lock-tables.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
