> > So if some rows couldn't be deleted, it should throw an error? Ignore it? > The delete method would throw an exception.
we've found that too hard a rule to follow. sometimes it's one bad record and it's a rollback then throw; othertimes it's go ahead and report the problem records for follow up. "it depends..." > > You don't plan on a msg to the user saying how many rows were deleted? > I wouldn't refactor to a "better" solution unless/until I could justify > the extra work and complexity. aye, I concur. On a needs basis only, not built-in. my 2c barry.b ---------------------------------------------------------- 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]
