At the very least, it knows that the application doesn't want to be told if the query fails. What if the application DOES need to know that, because it'll react differently than if the query succeeds?
Say you're a teacher. You tell your assistant "go get me the tests I need to grade." He comes back with an emtpy box and gives it to you. Lets hope you don't care if he failed at his task or if there just weren't any test to grade, because you don't get to make that distinction, your assistant is making it for you, without any input from you. Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryan F. Hogan > Sent: Tuesday, July 20, 2004 2:14 PM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] Making Persistant CFCs thread safe > > > I'm not saying that combining them is necessarily wrong, > but doing so it s a > > good way to paint yourself in a corner. > > You know it may, however at the moment I'm not convinced it > will. Having > an error handler that returns an empty query object when the code > expects a query object I don't see where that breaks > encapsulation. It > does not know anything about the application. ---------------------------------------------------------- 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]
