If you want to log query actions, then a trigger is the best, since it'll be pretty much error proof if set up properly. If you want to log business operations, then the DB/log4j distinction becomes a matter of how you want to use the data. Obviously having the log data in a DB facilitates easy report extraction (you just query the table(s)). On the flip side, logging to the DB is very likely going to be more resource intensive than logging to a file.
cheers, barneyb On 9/20/05, Michel Deloux <[EMAIL PROTECTED]> wrote: > Hi all > > what's the best choice to store users actions in a CF > application(inserts, updates and deletes)? DB or Log4J could be > resolve this? Anyone use log4j? Any approaches? > > Cheers > > MD > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:218712 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
