Bryan F. Hogan wrote:
Why not separate things out for yourself. This makes things easier for yourself and anybody in the future that may have to deal with your "mess".
Which is why Barney and I are having this conversation. Neither of our methods are Spaghetti and neither of condone the act.
I wasn't calling your method spaghetti - I have faith that you know what you are doing - otherwise you wouldn't be participating in this list. ;-)
However, I was pointing out that why have a method that only queries something perform some type of loose "error handling" and let the method do what it's suppose to do: Query the DB.
I'd pick up the error handling somewhere else...either on the calling template or in the method calling your query method. I can see how QueryNew()'ing your var scope makes things easier - however, if you let your calling template or method do the error handling (or even a larger scale here) you have a lot more granular controll on things and in the end could be easier to debug in the future if something happens or you wish to change something.
.pjf
----------------------------------------------------------
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]
