DatabaseAudit |
|
Your trail: |
Difference between
version 2
and
version 1:
At line 1 added 1 line. |
!!Database Auditing |
At line 3 added 2 lines. |
You might want to either audit who has changed the data, or what the specific data |
changes were. There are a number of options available to you: |
At line 6 added 1 line. |
* Use Spring Transaction Manager/Interceptor |
At line 10 added 1 line. |
* Hibernate auditing |
At line 14 added 1 line. |
* Database triggers |
At line 10 changed 4 lines. |
- The old style way of doing this is by using triggers and creating |
mirror audit tables for any tables you want to audit... this can be |
great if you have DBA's that will write this stuff for you!! (as you |
dont have to do anything!!) |
A traditional way of auditing what data changes have been made is by using triggers and creating |
mirror audit tables for any tables you want to audit (ie. user_audit). The triggers will fire when a modification to a record occurs, and write to the audit table, writing the state of the record and who made the modification. |
At line 15 changed 1 line. |
- Oracle 9i now has auditing built in ... |
* Oracle 9i now has auditing features built in |
At line 17 changed 2 lines. |
- A crude (but quick) way is to log it to a special file (maybe setup |
via log4j or something), any modifications... |
* You could use log4j to configure a special audit log file and write to that |
At line 20 changed 4 lines. |
- There are some software that sits inbetween DAO and DB to log this |
stuff already.. |
|
http://www.p6spy.com/ |
* You could software like [this|http://www.p6spy.com/] that sits between Hibernate and the DB |
Back to DatabaseAudit,
or to the Page History.
|