Dave Watts wrote:
recordset within another would break that model. In any case, I haven't yet
encountered a need to use this construct, so this discussion is fairly
academic to me.
well i could see the benefit for something like the cfpop query's mail
headers (though as a structure rather than
While I am aware of most of the alternatives, I'm more interested in
understanding the pratical reasons why this method is not used.
There would definitely be a performance problem, especially if the
sub-queries are big queries.
Although I didn't try it, I think one of these alternative would
Claude Schneegans
The result would be the same, but the sub-query would not have to be
copied into the main query, and there would be a difference on performance.
I would think that the sub-queries would not be copied into the main query.
In java, objects like structures are passed by
I suspect it has more to do with the fact that people have specific
expectations about what's in a query object than anything else. People have
a two-dimensional mental model of what a recordset is, and nesting one
recordset within another would break that model.
You may very well be right.
Because anybody looking at the code wouldn't at first understand what is
going on.
I don't think this is a good reason. If somebody looking at
cfset QuerySetCell(query2, ColumnName, query1, rowNumber)
is not able to understand what's being done, he better not have
access to the code anyway.
Thank you both for your responses.
Personnally, I'd be more interested in hearing why this would be a *good*
idea?
Primarily because query objects can be used with the cfoutput/cfloop tags which
IMO provide a simpler and cleaner method for accessing the related information
than structures or
I think my biggest problem with doing this is, the performance cost of
query objects. Aside from file handling query objects seem to be one
of the worst performing objects in coldfusion.
Adam H
On 7/21/05, HOFLee _ [EMAIL PROTECTED] wrote:
Thank you both for your responses.
Personnally, I'd
and am wondering if there is a good reason why.
That is the question.
One can sure use loops on queries inside loops on queries, but do we
need to store them inside each others ?
~|
Logware (www.logware.us): a new and
I think my biggest problem with doing this is, the performance cost of
query objects. Aside from file handling query objects seem to be one
of the worst performing objects in coldfusion.
Adam H
Yes, I would expect query objects to be more expensive than an arrays. Any
stats/links or
Claude Schneegans
That is the question.
One can sure use loops on queries inside loops on queries, but do we
need to store them inside each others ?
For the purposes of my question ... yes ;-)While I am aware of most of the
alternatives, I'm more interested in understanding the pratical reasons
For the purposes of my question ... yes ;-)While I am
aware of most of the alternatives, I'm more interested in
understanding the pratical reasons why this method is not
used.
I suspect it has more to do with the fact that people have specific
expectations about what's in a query object
For my own edification, I'm interested in learning the reasons why the
following would *NOT* be a good idea:
Storing a query object within another query object, like:
cfset QuerySetCell(query2, ColumnName, query1, rowNumber)
I am aware that you can accomplish a similar effect by constructing
]
Sent: Thursday, 21 July 2005 3:10 PM
To: CF-Talk
Subject: Query object contained within a Query object
For my own edification, I'm interested in learning the reasons why the
following would *NOT* be a good idea:
Storing a query object within another query object, like:
cfset QuerySetCell(query2
13 matches
Mail list logo
