C. Hatton Humphrey wrote: > Second is the fact that while you can look at the tables, extracting > the field names can be a different issue. For this I actually used a > lookup table that held the table name and column names of the columns > I wanted to log.
for insert & delete i would imagine that's a moot issue, in any case you have full access to the inserted and deleted "logical tables". for updates you can check which columns were involved as long as you understand where they are in the table using COLUMNS_UPDATED() (or individual columns using the "IF UPDATE (column_name)" syntax). the only real issues i've ever had w/triggers is that they won't get fired for TRUNCATE TABLE or WRITETEXT operations. i really would have thought triggers were ideal for tracking db changes, we use them all the time for this. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create Web Applications With ColdFusion MX7 & Flex 2. Build powerful, scalable RIAs. Free Trial http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270411 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
