Comments on: Trick for the Newbies http://www.sitepoint.com/blogs/2004/08/04/trick-for-the-newbies/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Fri, 19 Mar 2010 02:31:55 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Scott Barnes http://www.sitepoint.com/blogs/2004/08/04/trick-for-the-newbies/comment-page-1/#comment-7983 Scott Barnes Tue, 30 Nov 1999 00:00:00 +0000 236103637#comment-7983 <p>You can also achieve the same result but actually faster then the "group" attribute by doing this:</p> <p><cfoutput query="q"><br /> <cfset pRow = currentRow-1><br /> <cfset nRow = currentRow+1></p> <p><cfif groupField[nRow] NEQ groupField[currentRow]></p> <p>Start new distinction.</p> <p><br /> </cfoutput></p> You can also achieve the same result but actually faster then the “group” attribute by doing this:



Start new distinction.

]]> By: PaulWeston http://www.sitepoint.com/blogs/2004/08/04/trick-for-the-newbies/comment-page-1/#comment-7984 PaulWeston Tue, 30 Nov 1999 00:00:00 +0000 236103637#comment-7984 <p>That cfoutput query='x' stuff I tried a while ago and ended up with some considerable problems. It looks neater but there is a nasty side effect on queries inside queries. If you have a very complex scripted page and have a few of these embedded in another cfoutput query='x' type scenario you end up with strange results. I used to have a test piece of code that proved this in about twenty lines. The same issue occured from CF 4.5 through to 6.1.</p> <p>I now treat the resultset like an array. It has never failed since. If you're only going down 1 level (ie not nested) then there is no problem and your way works fine.</p> <p>I'd like to be able to claim I discovered this 'feature' on my own but it was after a bit of Googling around, someone out there broke it down why I was having problems and it all then made sense. I've lost the link but it's out there somewhere.</p> <p>- PaulWeston</p> That cfoutput query=’x’ stuff I tried a while ago and ended up with some considerable problems. It looks neater but there is a nasty side effect on queries inside queries. If you have a very complex scripted page and have a few of these embedded in another cfoutput query=’x’ type scenario you end up with strange results. I used to have a test piece of code that proved this in about twenty lines. The same issue occured from CF 4.5 through to 6.1.

I now treat the resultset like an array. It has never failed since. If you’re only going down 1 level (ie not nested) then there is no problem and your way works fine.

I’d like to be able to claim I discovered this ‘feature’ on my own but it was after a bit of Googling around, someone out there broke it down why I was having problems and it all then made sense. I’ve lost the link but it’s out there somewhere.

- PaulWeston

]]> By: Nate http://www.sitepoint.com/blogs/2004/08/04/trick-for-the-newbies/comment-page-1/#comment-7985 Nate Tue, 30 Nov 1999 00:00:00 +0000 236103637#comment-7985 <p>A lot of times problems with nested CFQUERIES can be solved by always scoping your query variables. For instance: Query1.Firstname, Query2.Firstname. This way you will never have variable collision...if that was the strange result you were experiencing. I remember having this problem back in CF 4.0 before I knew about scope.</p> A lot of times problems with nested CFQUERIES can be solved by always scoping your query variables. For instance: Query1.Firstname, Query2.Firstname. This way you will never have variable collision…if that was the strange result you were experiencing. I remember having this problem back in CF 4.0 before I knew about scope.

]]>