> Well, don't just take what I say at face value anyway - Nathan just said >they do, and he's a pretty smart guy!
You both are, so it gets confusing when one is on one side and the other another. :) That's why I asked for clarification. > The CFQUERY scope only exists until you run another query, so you already > have to copy it into another variable if you want to avoid having it > clobbered by the next query you run. Doesn't properly named queries exist for the life of the request? The only time I can see the query only lasting until another query is run is by naming two queries with the same name in the same request. I think this is what your said. >The CFCATCH scope only exists within a >CFCATCH block, and I think it's really unlikely that you'd have one CFCATCH >block clobber another, unless you invoke a component within a CFCATCH - and >even then, I'm not sure it gets clobbered anyway, although presumably it >would. Ok I understand that now. It looks like Nathan just verified that the first CFCATCH gets to keep it's dignity. :) > However, you probably can't go wrong by following Nathan's advice here, > since it doesn't hurt anything to create a couple more local variables. Your right, I have been following this advice, that's why your post originally was confusing to me. Thanks for your post. Bryan ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word '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]
