Cfquery: name and result

[michaeldiederich]

(Unsure if dev, dev-support or language…)

After the feedback about the “slow” OOO implementation of Query(), I had a deeper look at cfquery().

The function has 2 parameters, name and result. From my point of view, name is for attributes and result has the result of the query.

<cfscript>
cfquery(datasource="test", name="qInsert", result="qInsertResult", sql="INSERT INTO test (foobar) VALUES ('#createUUID()#')");
writeDump(structKeyExists(variables, "qInsert")); // false
writeDump(structKeyExists(variables, "qInsertResult")); // true
writeDump(qInsertResult);

cfquery(datasource="test", name="qSelect", result="qSelectResult", sql="SELECT * FROM test");
writeDump(structKeyExists(variables, "qSelect"));
writeDump(qSelect);

writeDump(structKeyExists(variables, "qSelectResult"));
writeDump(qSelectResult);

</cfscript>

Insert: Name doesn’t exist
Insert: Result shows the meta-data for the query

Select: Name shows the result of the query
Select: Result shows the meta-data for the query

(For reference:
Update: Name doesn’t exist
Update: Result shows the meta-data for the query)

Am I missing some kind of system or pattern here?

[Zackster]

insert and update don’t produce result sets?

[michaeldiederich]

Quote: From my point of view, name is for attributes and result has the result of the query.

Well, I was refactoring the code, and replaced a function with cfquery. I was confused, that I can set the attribute name, but not access it (for update or insert). That the attribute result has not the actual result, but only meta-data and that the name attribute for SELECT has the actual result.

I excepted, that all queries have a name attribute (e.g. cache, query runtime, maybe created keys or so) and the SELECT has a result to use the result of the query.

[Zackster]

Leaving the attribute naming aside and the historical nature (tech debt) of cfquery, the logical separation is pretty clear?