LOL. Yeah, sorry-- I see "idea" and I'm off. ;-) I forgot there was a real application we were contemplating, vs. just philosophy of how to achieve X.
For thread justice: The way I've handled it, in a similar case, was with a duplicate table. Assuming you've got your DB code abstracted to a central place (to totally misuse abstract, probably), it should be a snap to add a secondary insert into the duplicate table whenever an update occurs. Then add a function that loops through those records, and creates a "diff" for the modified fields. Theoretically you could even re-use the "view" portion of your code and thus preserve field names or whatnot. Theoretically. =] On 2/21/07, Judah McAuley <[EMAIL PROTECTED]> wrote: > > Just so my previous email doesn't get drowned out in a debate over ajax, > if I were tackling this problem, I would have a hidden form field on > each page that lists the fields that have been changed. Attach an > onChange handler to each form field that the sys managers can change. > Have it call a function that simply adds the id of that form field to > the hidden form field. On the form submit, just look go through the list > of changed fields and log the before and after data. Quick and dirty and > requires minimal change to your existing setup. > > Judah > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270424 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
