tnx, i mean exactly the second choice you explain.
Everytime that a user call /controller/action i have to update the
fields,
 so i'll have to use beforeFilter in AppController.


On 23 Feb, 16:30, jeremyharris <[email protected]> wrote:
> Depends what you mean by "make an action." Do you want to modify the
> timestamp each time they modify the database, or do you want to modify the
> timestamp each time they call an action, like /controller/action?
>
> If it's the first, then use a behavior. There are a few "logging" behaviors
> out there that will do this for you (i.e., This user modified this model id
> on this date).
>
> If it's the second, then a simple beforeFilter on AppController will
> suffice.

-- 
Our newest site for the community: CakePHP Video Tutorials 
http://tv.cakephp.org 
Check out the new CakePHP Questions site http://ask.cakephp.org and help others 
with their CakePHP related questions.


To unsubscribe from this group, send email to
[email protected] For more options, visit this group at 
http://groups.google.com/group/cake-php

Reply via email to