|Subject||RE: [ib-support] Audit Trail/Log implementation (or How to loop through fields)|
> > Thomas Steinmaurer provides an inexpensive tool calledIf you have any questions about licensing, then feel free to contact
> IBLogmanager which
> > will create all triggers and logging tables automatically for
> > you. Takes you a few minutes no matter how complex your DB-Design is.
> > Works quite good and has a nice UI.
> Thank you for the pointer. But the "inexpensive" part is probably
> open for debate...:) You have to pay additional license
me privately. (ts@...)
> The problem is that it's "hard coded".IBLM 2.0 provides a very easy to use UI. If you add a new column to one of
> When someone (maybe you) come and modify your table structure (adding a
> etc), it will break the logging functionality; or force you to modify the
> itself, hence the idea of using IB's metadata (if possible) instead of
> field and table names.
your table, within IBLM 2.0 this column is shown as "not registered for
Double-click the column name for the specific data manipulation operation
delete/insert/update and IBLM 2.0 ensures, that the trigger is recreated
> AFAIK, there are two general approach on the logging data itself,IBLM 2.0 uses the second approach too ...
> either you create identical copy of your actual tables for
> dumping the data,
> or we could use a central log table for all the logged activities. I use
> the second approach because it only uses one or two additional tables.
We should discuss any IBLM related things up now privately (if you like).
IB LogManager 2.0 - The Logging Tool for Interbase/Firebird