Skip to main content
S
Steve Sommers
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
    BKBKCommunity Expert
    Community Expert
    July 17, 2016

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

    WolfShade
    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,

    ^_^

    S
    Steve SommersAuthor
    Legend
    July 20, 2016

    Try this:

    <cfscript>
        qTable = QueryNew("id,title" , "integer,varchar");
        queryAddRow(qTable, {"id"=1,"title"="Dewey defeats Truman"});
        qryResult = QueryExecute("SELECT * FROM qTable", {}, {dbtype="query"});
        WriteDump(qTable);
    </cfscript>

    Tested on CF11/CommandBox.

    -Carl V.


    That works but I'm using FW/1 and I believe the default variables scope is the CFC instance which is a shared instance. This might run into threading collisions. For now I copy the query result set to the request scope (rc in FW/1 context) and this is working, it just smells of slimy hack.

    rc.qTable = local.qTable;

    local.qryResult = QueryExecute("SELECT * FROM rc.qTable", {}, {dbtype="query"});

    But then again, "rc" is using the default variables scope in this sample. Hmmm...

    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
      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
      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.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices