<cfquery> bug/missing function

[Sir Monkey]

Hi All,

In the docs there are a few references to SQLParameters being a member of
the new results structure. The docs say the use is something like:

<cfquery ... results="tempVar">
SQL BLAH
</cfquery>

<cfdump var="#tempVar.SQLParameters#">

It's supposed to hold an "ordered array of cfqueryparam values". What I'm
hoping that means is an array of column types (VarChar, Integer, etc). But for
the life of me, I can't find it. It doesn't show up in the results at all...no
matter what I do.

Am I doing something wrong?

Also, if it is indeed an array of column types...why is it an array? The
column names are passed out as a list, why not pass the column types as a list
as well? It would make life easier if you are trying to do something like
<cfset rstStuff = QueryNew("#rstOriginal.columnList#",
"#rstOriginal.columnTypes#").

TIA,
Chris

[OldCFer]

I'm seeing it OK. What it dumps is the sequence 1,2,3 etc along with the value 100,John,Mary etc

[Jochem van Dieten - TMM]

Sir Monkey wrote:

>
> In the docs there are a few references to SQLParameters being a member of
> the new results structure. The docs say the use is something like:
>
> <cfquery ... results="tempVar">
> SQL BLAH
> </cfquery>
>
> <cfdump var="#tempVar.SQLParameters#">
>
> It's supposed to hold an "ordered array of cfqueryparam values". What I'm
> hoping that means is an array of column types (VarChar, Integer, etc).

That's not what it means.

If you use cfqueryparam all the variables in the normal debug
output are replaced by placeholders, i.e.:
SELECT * FROM table WHERE field = <cfqueryparam value="xCFx">
will show in the debug output as:
SELECT * FROM table WHERE field = ?

In this case the SQLParameters array will hold the pair
1 xCFx so you know the value that was substituted for the first
parameter.


The information you want is not available from CF. Which does
make a bit of sense, CF itself is typeless.

Jochem

--
Jochem van Dieten
Team Macromedia Volunteer for ColdFusion, beer and fun.

[Sir Monkey]

On one hand, I'd agree that leaving the column types out makes sense in a
typeless language...on the other hand SQL is typed (as are recordsets and query
of queries). And when you create a query with QueryNew MM recommends that you
supply a list of column types along with the column names. In a situation
where you creating a forged recordset from a real one, it would be very helpful
to be able to programmatically pull the column types from a query. While CF
makes pretty good guesses most of the time, it interprets one of my columns
that should be a string as a date (the data is in the format ?0000-00000-0000?).

Maybe this will come about in CF 8?

Thanks all!!

Chris

[Jochem van Dieten - TMM]

Sir Monkey wrote:

>
> Maybe this will come about in CF 8?

[url]http://www.macromedia.com/go/wish/[/url]

Jochem

--
Jochem van Dieten
Team Macromedia Volunteer for ColdFusion, beer and fun.