"Adam Cameron" wrote >> Each DB table has a CFC that relates to it, and might have methods like get(), >> add(), update(), delete(). The get() function will take an argument for each field >> of the table, to allow filtering (basically chucking it in a where statement), as >> well as an additional 'whereClause' argument for stuff that ain't a direct >> col=value filter.
so, by abstracting the persist/data layer in this way, how are you able to deal with transactions - esp with multiple tables (and therefore multiple CFC's)? I thought it wasn't possible to transact accross multiple CFC's - at best accross multiple methods within the same CFC. At the moment I'm trying to keep as much logic as poss within the controller and leave the persist/data layer a bit light on. thanx barry.b -- _______________________________________________ Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! http://www.net2phone.com/cgi-bin/link.cgi?143 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
