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 wrot
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 t
You could do some manual work using timestamps and such. So in other
words, you read in the record and check whether the timestamp has been
modified since the current user has worked on it, if so return an error
message.
It can get a bit complicated in the implementation but this is how it
used t
Right. Silly me, I mixed up the two when in fact they are incompatible.
They do share innodb however. I apologize for that.
Sorry, I can't be very helpful in this regard.
I would, however, have high hopes for a couple custom queries. I
_think_ it would be something like this:
$this->query("LO
Hi Calzone
I don't believe that transactions are what I need here (but thank you
for the suggestion).
A typical issue that I would want this system to handle is:
1. User 1 opens a record to edit it
2. User 2 trys to open the same record before User 1 has completed
his/her edit
3. System ret
I believe Cake supports transactions.
See http://manual.cakephp.org/chapter/6 search for $transactional on
the page
Outside of that, I imagine you could pass custom queries to lock and
unlock, but I'll let someone else comment on these possibilities.
--~--~-~--~~~--
Hi
I am designing an application that requires locking of data during
editing to avoid conflicting edits. Not just locking of an individual
record in the database, but of a record and its related records.
I have never heard of this sort of functionality being implemented in
Cake, so thought
