Object Logging Library

@Inc33 I will look into it. At the time of this module the afterInsert and afterUpdate events didn’t contain sufficient data without making a second database call, which would be a big performance hit. The events have since changed so I will see how viable that is.

You'r right, it's a dangerous path. But it is possible to do it, even if only contains the new values, as you can somehow get back the older values from the previous entry.
But if you have that, then you can basically create a trigger based event system in your app, and do a lot of cool stuff