db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michel Beijlevelt" <...@lucka.nl>
Subject Re: **** AUDIT TRAILS ****
Date Mon, 28 Jul 2003 13:37:33 GMT
Howdy,

you *could* use Log4J for this, but why would you? You could also store
this audit trail in the database. This has some advantages: you can
restrict a user to access only data that (s)he created or owns. You can
query the database for the audit trail, it becomes a sort of management
information.

I guess you should change your datamodel for that, e.g. add 'created_by'
and 'changed_by' columns to the tables to which you whish to apply the
audit trail to. Then, you can change some of the bases classes to log the
audit trail for each operation.

Mind you, this would be easier to build when using database users because
they are known to the Torque framework. In your case, by some means you
have to supply the application user id to the methods that perform the
logging of the audit trail.

HTH, gr. Michel

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message