Skip to main content
Legend
July 15, 2016
Answered

Query scope descrepancy between tag and script

  • 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*/

<cfquery name="local.qResultSet" result="local.qResult" dbtype="query">

    SELECT

        *

    FROM

        rc.qRSRecipient

    where

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

</cfquery>

/* exception */

<cfscript>

    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");

    3 replies

    BKBK
    Community Expert
    Community Expert
    July 17, 2016

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

    WolfShade
    Legend
    July 18, 2016

    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
    July 20, 2016

    Unfortunately for me, it's a little more complex than that. I love FW/1 for it's leanest and low overhead but I incorporate "fuses" from fusebox using includes for small (at least I try to keep them small) qry and act modules. With includes for some reason you cannot declare "var xxx" as it squawks that var can only be used in a function -- even though the module is being included within a function. Another topic for another thread. I will experiment with this a little more. It seems close.


    Can you "var" scope the variable above the include statement?  Will that carry through into your "fuse"?

    BKBK
    Community Expert
    BKBKCommunity ExpertCorrect answer
    Community Expert
    July 17, 2016

    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
    July 15, 2016

    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
    July 15, 2016

    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.