As far as your last question is concerned, alas, I have no insight. But I am curious about your
"wrapper" around cfquery. We use cfqueryparam to enforce type-safety as well as allow the DBMS to
cache the query plan (hence performance boost). By using a wrapper around cfquery, I am using your
"name" attribute to cfquery is always the same? (or you randomly generate a number or use a UUID?).
This might be bad. My understanding is that the name for the query is how CF keeps track of the
query. By using one name, I dont think CF can accurately track what is going on, and/or you might
not be able to use cfqueryparam at all. But if you are just passing in a string to your cfquery
wrapper (your SQL), then you are probably not using cfqueryparam at all (I think it has to be called
as a child of cfquery). So I guess that pretty much negates my question. I think cfqueryparam is
great and while I do prefer cfscript over tag-based CF, losing cfqueryparam just for vanity's sake,
its definitely *not* worth it.
Please correct me if I am wrong.
/Cody
Jimmy Glass wrote:
Morning,
Personally, I feel that CFSCRIPT code is much prettier than a tag based CFC.
But, my intent is not to spark a debate on the elegance of using tags. In
instances where my functions require a tag, I generally use a CFC that I've
built which contains functions that interface with the tag. CFQUERY, CFDUMP,
etc. I'm sure this is a rather common technique.
What I do like about the CFFUNCTION/CFARGUMENT tags are the ability to
explicitly define the return type and output of a function, and the data
types of the arguments. To my knowledge, this is not possible when defining
a function w/ CFSCRIPT.
Does anyone have a work around, or a way of accomplishing this in CFSCRIPT?
Thanks,
Jimmy G
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
