And one more post to clarify, I assumed that ALL of your models would
have those fields present ('created_on', 'created_by', 'updated_on',
and 'updated_by'). If a subset of models only need to record that
information, I'd override the afterSave() method in a base class that
extends from AppModel, and then extend my models off of it.

The requirements for my project are a little different. I need an
entire table that records the update times, user ids, what was
modified, how it was modified, what is the new value, etc. for
accounting and rollback purposes. As long as my accounting table is
associated with the model being recorded, I might be able to use a
similar solution to automate it with the afterSave() callback. Still a
fresh thought - more to research and think about...


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to