Can anyone confirm that this is how it is supposdto work?
Actually, this is how it does work.
IMO it is for the least a serious flaw in the design. There is no reason
the current row
should be implicit for the most inner level of the loop only.
--
___
REUSE
Srinivasa Teja Palla wrote:
I was doing a
cfloop query=outerQuery
cfloop query=innerQuery
cfoutput#outerfieldvalue# #innerfieldvalue#/cfoutput
/cfloop
/cfloop
outerfieldvalue is a fieldname unique to the outer query, however when I do
the loop, for all outerloop iterations, I noticed it
Jeff D. Chastain wrote:
I was referring to the inner query using the full scoped name -
variables.queryName.
So, why does setting newQueryName = variables.queryName PRIOR to looping
the first query change anything? Both variables are in the variable
scope and are created prior to the first
is null. For some reason the variable is just gone.
Thanks
-Original Message-
From: Zac Spitzer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 8:23 AM
To: CF-Talk
Subject: Re: Nested Query Loops
Jeff D. Chastain wrote:
I was referring to the inner query using the full scoped
Jeff D. Chastain wrote:
I am not even making it that far. I am getting an error on cfloop
query=qry2 stating that qry2 is not a recordset. If I do a cfdump
prior to the first loop, qry2 is a recordset with several rows of data.
If I do a cfdump right before the second loop (i.e. inside the
Nope, all names (query and column) are different between the two
queries.
-Original Message-
From: Zac Spitzer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 9:21 AM
To: CF-Talk
Subject: Re: Nested Query Loops
Jeff D. Chastain wrote:
I am not even making it that far. I
-vancouverisland.com
- Original Message -
From: Jeff D. Chastain [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, December 02, 2002 3:25 PM
Subject: RE: Nested Query Loops
Okay, what do you mean by properly referencing the
queries?
I always use the queryname.columnname inside of a
loop
I was referring to the inner query using the full scoped name -
variables.queryName.
So, why does setting newQueryName = variables.queryName PRIOR to looping
the first query change anything? Both variables are in the variable
scope and are created prior to the first loop - they should be the
]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, December 02, 2002 2:30 PM
Subject: RE: Nested Query Loops
I was referring to the inner query using the full scoped name -
variables.queryName.
So, why does setting newQueryName = variables.queryName PRIOR to looping
the first query change anything
Ticket
application.
- Original Message -
From: Jeff D. Chastain [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, December 02, 2002 2:30 PM
Subject: RE: Nested Query Loops
I was referring to the inner query using the full scoped name -
variables.queryName.
So, why does
.
-- Jeff
-Original Message-
From: Bryan Stevenson [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 4:34 PM
To: CF-Talk
Subject: Re: Nested Query Loops
Well...think about your nested loop having fieldnames that same as the
outer loop
CF has to know which field you
- Original Message -
From: Jeff D. Chastain [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, December 02, 2002 2:39 PM
Subject: RE: Nested Query Loops
I can see that ... The issue is that I have two differently named
queries with differently named columns. The CF error
-Original Message-
From: Bryan Stevenson
[mailto:[EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 4:45 PM
To: CF-Talk
Subject: Re: Nested Query Loops
I beleive this is the case ALWAYS even if the 2 queries
have seperate names
and fields. This feature is there to prevent the
issue I mentioned
- Original Message -
From: Jeff D. Chastain [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, December 02, 2002 3:25 PM
Subject: RE: Nested Query Loops
Okay, what do you mean by properly referencing the
queries?
I always use the queryname.columnname inside of a loop,
even
14 matches
Mail list logo
