That sounds like you need (1) a tool for analysing the commit log. (2) Some kind of API for events that aren't in the commit log, where you can plug in a class that implements the API and record the events.
Patches welcome :-) Thotheolh wrote: > Hi. After playing around with the trace log level, I noticed that none > of them could actually be used to accurately trace events and perform > audits and security based activity. Some database calls it the C2 > auditing function. Would some form of auditing function be available > in the near future to audit events, changes made, user logins, ddl and > dml based changes and stuff relating to auditing and security ? > > Is there some ways to tap into the main H2 database transactions so > that if necessary, a set of security auditing tools could be developed > externally by interested parties that would interface with H2 and > provide more specific auditing logs that would aid in scenarios where > H2 would be deployed in large enterprise environments ? > > In my opinion, H2 should not be too bulked down by too much > involvement in auditing and let the security audit providers and > developers do their development for H2 if security auditing would make > H2 more bulkier. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
