Pierce T. Wetter III
This gets discussed a lot, so there's plenty of examples around. For instance, here's an implementation by someone else I found via Google: http://homepage.mac.com/i_love_my/code.html
...
Code Block |
---|
override saveChanges() self.processRecentChanges() foreach obj (self.changedObjects) obj.auditTrailChanged() foreach obj (self.insertedObjects) obj.auditTrailChanged() foreach obj (self.deletedObjects) obj.auditTrailChanged() super.saveChanges() |
Houdah Frameworks:
(scooped from the mailinglist)http://www.mail-archive.com/webobjects-dev@lists.apple.com/msg25686.html
Take a look at Houdah Frameworks. I think the Audit Trail WO:1 WO:2 solution provided by this framework could be helpful.
The Wonder Bug Tracker application also includes support for audit trail. Maybe you can learn something from there.
#1 http://code.google.com/p/houdah-webobjects-frameworks/wiki/HoudahAuditTrail
#2 http://code.google.com/p/houdah-webobjects-frameworks/wiki/AuditTrail
Dov Rosenberg
(scooped from the mailinglist)http://www.mail-archive.com/webobjects-dev@lists.apple.com/msg25683.html
Most of the projects I worked on with this requirement used the built in audit tracking functions of the database. Most DBA's didn't leave the requirement to the developers to enforce. That way everything is tracked in a consistent fashion across applications.
Ken Anderson
(scooped from the mailinglist)http://www.mail-archive.com/webobjects-dev@lists.apple.com/msg25691.html
...