Model events and observers should be the right way to achieve this goal. Take a look at: http://laravel.com/docs/eloquent#model-events

longilineo said:

Model events and observers should be the right way to achieve this goal. Take a look at: http://laravel.com/docs/eloquent#model-events

Yes, this might be working - but I didn't find any example, describing what to do to use this feature.

But as far, as I see, I need to check out the current and the future values manually - as well as comparing them. Using mySQL triggers, I do have the old and the new values there as an instance...

if you don't want to implement from scratch your own audit mechanism, give a try to this package: https://packagist.org/packages/venturecraft/revisionable

Thanks - I will checkout this...

Sometimes, it's difficult for a non native speaker to join name and action. I would have not used the term "audit" for the thing I want to do ;-)

Ciao

dirk