>How valid is this, Perfectly so. With the one caveat that you're find that query-of-query really won't like it. Then again there's far more fundamental things than *that* which QoQ also doesn't like, so it's in good company.
>if so, is there a possbility that it will it ever cease to be valid? I sincerely hope not. We use this construct all the time. >I don't think a result set directly from a database could ever generate this, I guess what I am saying/asking is "Is this really a query, or just cf telling my its a query"? I think you're putting the cart before the horse. CF gets a resultset from the DB driver and places the data from it in a query object. It doesn't *arrive* from the DB in that format. Theer is no causal link between the two. One additional thing to be mindful of when using complex data, though, is that structs and queries are copied by reference, so if - using your example - you change data in qTest2, you will see that change reflected in mystruct.test2 and qTest1.column2[1].test2 as well: it's all the same memory. This is good when it's your intent, and it's certainly useful when passing large structures and queries (and combinations of the two!) around the place... You're passing the reference, not all the data. But it can get very confusing very quickly if you change data in one place and suddenly see itchanging elsewhere too :-) Adam Cameron Senior Application Developer Straker Interactive Ph: +64 9 3605034 Fx: +64 9 3605870 Email: [EMAIL PROTECTED] --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
