> This has always been the behavior of CF. I can agree that it at first
> glances appears to be counter intuitive, but at the same
> time, any reference
> to queryname.fieldname outside the context of a <CFLOOP> or <CFOUTPUT>
> results in a reference to the value of the field in the first
> row of the
> query. The functionality is such that there is no "inheritance" of
> references.
Well, I think you're at risk of sounding like an apologist for Allaire.
There are a couple of things that I feel need "fixing" in ColdFusion, and
this is one of them (the other one that springs to mind is the inability to
optionally specify that empty list elements aren't ignored - really useful
if you are populating database tables from delimited lists).
<CFOUTPUT QUERY="GetParents">
*Crappy CFSET GetParents.ParentID code required here*
<CFOUTPUT QUERY="GetChildren">
#GetParents.ParentID# doesn't increment properly with each
iteration of the outer loop.... WHY NOT ALLAIRE?!?!
</CFOUTPUT>
</CFOUTPUT>
> Since CF5 is feature complete and in RC testing, I would
> seriously doubt
> that a change in behavior is going to happen in this release,
> or for that
> matter even in NEO.
Unfortunately, I think you might be right.
"Hey, we've fixed a load of old bugs!" doesn't sound as good to new
customers as "Hey, there's a load of new features!".
--
Aidan Whitehall <[EMAIL PROTECTED]>
Netshopperuk
Telephone +44 (01744) 648650
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
