Legend

Answered

Query scope descrepancy between tag and script

Forum|Forum|9 years ago
July 15, 2016
3 replies
2112 views

I'm fairly certain I found a scope bug. I'm using CF11 and FW/1 and I have the following query -- the tag works, the cfscript equivilent triggers a "Table named rc.qSignerLinks was not found in memory" exception:

/* works*/

SELECT

*

FROM

rc.qRSRecipient

where

[email] = <cfqueryparam value="#session.user.getEmail()#" cfsqltype="CF_SQL_VARCHAR" maxlength="50" />

</cfquery>

/* exception */

local.qObj = new query();

local.qObj.setDBType("query");

local.qObj.setSQL("

SELECT

*

FROM

rc.qRSRecipient

where

[email] = :email

");

local.qObj.addParam( name="email",value="#session.user.getEmail()#",cfsqltype="CF_SQL_VARCHAR",maxlength="50" );

local.qObjResult = local.qObj.execute();

local.qResultSet= local.qObjResult.getResult().recordCount NEQ 0;

</cfscript>

This topic has been closed for replies.

Correct answer BKBK

Yes, Steve, that problem has been known for some years now. The usual fix is to add the resultset using setAttributes(), like this:

local.qObj.setAttributes(tbl = rc.qRSRecipient);

local.qObj.setSQL("SELECT * FROM tbl WHERE [email] = :email");

BKBK

Community Expert

Having said that, I still think you should file a bug report.

WolfShade

Legend

I'm not sure I'd classify this as a bug. I mean, granted, it does not act the same way as the tag-based CFQUERY, but not placing the query-to-be-queried within the same scope as the QoQ doesn't really seem like a bug, to me.

V/r,

^_^

Carl Von Stetten

Legend

I do understand that the error occurs because the context of the local variable, rc.qRSRecipient, is absent from the Query CFC. My point is that the error message is inconsistent, confusing. To see this yourself, put it alongside a phrase from your last post:

rc.qRSRecipient does exist in memory - but... Table named rc.qRSRecipient was not found in memory.

I think this just confirms what a bad idea it was to try to implement script functions as CFCs, rather than as built-in functions. I'm not sure how the error message could be fixed (and it is the error message that should be fixed - again the CFC is working as designed), since the error is not coming from inside the CFC - it's a ColdFusion runtime error.

It's actually coming from the execution of an actual CFQUERY call by the query.cfc (via inheritance from base.cfc, and the invokeTag() function). And running an actual CFQUERY as a Query-of-Query also gives this error:

I tested this on CF11 via CommandBox.

So if any bug report needs to be filed, then the error message for QofQ CFQUERYs should be changed to "Query named xxx was not found in memory". The bug report should not be against query.cfc.

-Carl V.

BKBK

Correct answer

Community Expert

Yes, Steve, that problem has been known for some years now. The usual fix is to add the resultset using setAttributes(), like this:

local.qObj.setAttributes(tbl = rc.qRSRecipient);

local.qObj.setSQL("SELECT * FROM tbl WHERE [email] = :email");

WolfShade

Legend

Not sure if this will help, but there is a Ben Nadel post about CF9's "query.cfc" and using a cfscript qoq. I hope it might present some insight.

I've never tried to run a standard query in cfscript, much less a QoQ in cfscript.

HTH,

^_^

Carl Von Stetten

Legend

You might also try looking at the new queryExecute() function introduced in CF11 for script. It usually works better than the query.cfc-based script approach.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded