CF7 has a built in variable that gets returned with every query. It contains
the actual final query language. It's [query_name].sql.
http://www.cfquickdocs.com/?getDoc=cfquery
-Original Message-
From: Richard Colman [mailto:[EMAIL PROTECTED]
Sent: Monday, January 22, 2007 1:33 PM
To:
Well, you could start by throwing the SQL query code into a var to begin
with:
cfset SQLVar = Select * from table
Or build it up as you would build it within the cfquery tags.
Then execute it:
cfquery etc etc
#SQLVar#
/cfquery
And since it's already in a var, you can write it to your DB as
The only way I've done that before is to do something like:
CFSaveContent variable=a
Select * from blah
/CFSaveContent
CFQuery ...
Select * from blah
/CFQuery
Basically writing the query twice. It kinda sucks, but that's the only
way I've thought of. Also, if your real sql contains
Dude! That's cool. Now I *really* wish I was running on CF7. :o)
Rick, I probably should have stated that my way is what I do in CFMX6.1
Chris
Andy Matthews wrote:
CF7 has a built in variable that gets returned with every query. It contains
the actual final query language. It's
Yeah, but you'd still have a problem when using CFQueryParams. :o'
Chris
Scott Weikert wrote:
Well, you could start by throwing the SQL query code into a var to begin
with:
cfset SQLVar = Select * from table
Or build it up as you would build it within the cfquery tags.
Then execute it:
I am not sure if this solves your problem, but if you have debugging turned
on the server, you can get several information from the servicefactory
debugging object. Here is a UDF that I wrote a while back which return true
if the query ran was a cached one.
http://www.cflib.org/udf.cfm?ID=1202
6 matches
Mail list logo