> > 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.
By default, the query itself exists for the life of the request as a variable, but the CFQUERY scope - which is something completely different - only lasts until you run another query: <cfquery name="qFoo" ...> SELECT * FROM foo </cfquery> <cfoutput> Record count: #qFoo.RecordCount# Execution time: #CFQUERY.ExecutionTime# </cfoutput> Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ---------------------------------------------------------- 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]
