I do something similar to this using ColdSpring's Aspect Oriented Programming. AOP allows me to check for any number of changes to various pdate functions without modifying the update functons themselves.
At a basic level it works as you described. I create an unchanged bean and a changed bean and send those both to the update function. I use a list of fields to compare as I don't need to compare all fields. You could use the list of form fields coming back from the post and either weed out the fields that you don't make sense to compare (
i.e., the submit button, formfields, hidden id fields...) or create a list of fields manually.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
- [CFCDev] How to detect changes at commit time? Mike Kear
- Re: [CFCDev] How to detect changes at commit time? Barry Beattie
- Re: [CFCDev] How to detect changes at commit time? Aaron DC
- Re: [CFCDev] How to detect changes at commit time? Matt Williams
- Re: [CFCDev] How to detect changes at commit time? Nando
