From: Adam Lubell <lubell@ec...> - 2003-07-25 11:59:31
Thanks for your reply Marcus. I had a similar reply from Sean Corfield at
There is no built in mechanism to Lock Records, and you have to approach
it similar to the way you approach any other SQL programming within a PHP
page. Options include: Locking a Table, Locking a Row, Locking out the
whole SWF so only one person can login at a time, or checking/warning if
there was already a change before the commit. (Hadn't thought about the
last one, and it will be the easiest for my case -- both Marcus and Sean
suggested this). Sean also suggested that if I'm using something like
FlashComm, I could detect the problem in real time, but this is beyond my
skills and is not warranted for this project.
Thanks for the help.
> Subject: [amfphp] Record locking
> I'm using AMFPHP in the administrator portion of my site. I have category
> names with descriptions stored in various MySQL tables. A user gets a SWF
> that allows viewing. An administrator gets a slightly modified SWF that
> also has update and delete buttons for modifying some of the information.
> If one administrator makes a remoting call to get a set of data for
> modification, I need to prevent another administrator from also getting
> the same
> data for modification. (A normal user that makes a remoting call for
> viewing only, without UPDATE privledges, is OK).
> Does AMFPHP and/or remoting in general (ie CFMX) have a _simple_ defined
> way of
> locking records? My impression is no. My current plan is to put extra
> column(s) into every relevant
> table to to set/check a locked condition, but then I'll need lots of extra
> stuff to track which user locks the record, when their session expires (if
> they forget to unlock), and extra validation everywhere (client and