Comments on: cfquery ‘result’ attribute caveat

By: Ipee

Ipee — Fri, 02 Dec 2011 14:30:48 +0000

Can anyone tell how to get the next row, if the query used in cfquery tag having maxrows attribute? mean to say, if your query extracts maxrows = 100, how to get the 101st row ?

By: Michael Sharman

Michael Sharman — Wed, 06 Aug 2008 00:08:06 +0000

@Allen – agreed for production ready code which is when I really don’t want the “result” attribute.

My data access objects typically return a “query” object, not a struct.

So using the request scope in this example is handy for development purposes only.

Good point though.

By: Allen

Allen — Tue, 05 Aug 2008 22:54:50 +0000

If you’re putting variables set in a method to the request scope, you’re code is no longer loosely coupled. You’re essentially using the method as a glorified CFINCLUDE. You should be returning the result structure just as you would return the name query.

By: Michael Sharman

Michael Sharman — Tue, 18 Dec 2007 18:39:13 +0000

Nice tip Adrian, thanks

By: Adrian Lynch

Adrian Lynch — Tue, 18 Dec 2007 14:01:23 +0000

Another tip, when you’re viewing the SQL, wrap it in pre tags to format it as it was typed in the cfquery tags.

By: Derek Versteegen

Derek Versteegen — Fri, 06 Jul 2007 15:47:04 +0000

Nice find – works like a charm – thanks.

By: Christopher Wigginton

Christopher Wigginton — Tue, 10 Apr 2007 14:40:01 +0000

bummer, there was some nice example code, but the blog stripped out the comments rather than encode the output. oh well. The gist of it was to use result=”this.result” which sets a property of the cfc which persists with the object instance.

By: Christopher Wigginton

Christopher Wigginton — Tue, 10 Apr 2007 14:37:43 +0000

—– In the CFC cfquery tag

———————-

This is just an example, you could certainly set a result name for each function/cfquery which would persist in the object instance.

The other option would be to combine the returned result and query as a deep structure