With the exception of the "adding a new field in the DB and it's avaialable evrywhere" bit, the other examples are easily handles by CFCs....one method to update...another to insert...they do different things...just like your example:
> def validate_on_update > #stuff > end > > or > > def validate_on_create > #stuff > end Same goes for validation on Insert/update...seperate methods to handle them....so no bonus with RoRo there. Now the "add a field" bit you mentioned....well just because "everything" knows about the new field does NOT mean that "everything" knows what to do with it.....so back to having to add custom code tweaks to make "everything" handle that new field correctly. No sale here....try the Vogons..they're big on super highways...mabye they'll see the light that I cannot ;-) Cheers Bryan Stevenson B.Comm. VP & Director of E-Commerce Development Electric Edge Systems Group Inc. phone: 250.480.0642 fax: 250.480.1264 cell: 250.920.8830 e-mail: [EMAIL PROTECTED] web: www.electricedgesystems.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238203 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
