Skip to Content.
Sympa Menu

freetds - RE: [freetds] ODBC limitations?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] ODBC limitations?
  • Date: Mon, 3 Mar 2003 14:10:16 +0100

>
> First one observation - I was using exec direct. The failure is
> different with Prepare. Is this a case of a driver being too
> considerate
> too us (and that we really should have used prepare and we're
> very very
> naughty people?)
>

I fixed problem for SQLExecDirect in CVS.

> Anyway, I switched to using prepare, and I now get an error
> about using
> a binary.
>
> The code we use is:
>
> unsigned char magicfun[1024];
>
> SQLBindParameter(hStmt, //StatementHandle
> 2, //ParameterNumber
> SQL_PARAM_INPUT, //InputOutputType
> SQL_C_BINARY, //ValueType Input
> SQL_BINARY, //ParameterType Actual
> Table Type
> 1000, //ColumnSize
> 0, //DecimalDigits
> magicfun,
> //ParameterValuePtr
> len, //BufferLength
> &len);
>
> Now, going just from what is in the debug log, this isn't being sent.
>
> It's an improvement over not using prepare, as it places a 0
> instead of
> a question mark, but is there a calling error here?
>
> Relevant bits from hte debuglog.
>
> Sending packet @ 2003-02-27 17:26:21.675048
> 0000 01 01 00 36 00 00 01 00 5b 00 73 00 70 00 5f 00 |...6....
> [.s.p._.|
> 0010 69 00 6e 00 73 00 65 00 72 00 74 00 43 00 68 00 |i.n.s.e.
> r.t.C.h.|
> 0020 61 00 72 00 61 00 63 00 74 00 65 00 72 00 5d 00 |a.r.a.c.
> t.e.r.].|
> 0030 28 00 30 00 29 00 |(.0.).|
>

Does sp_insertChar accept binary/integer data?
Have you set up len parameters?

freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================



  • RE: [freetds] ODBC limitations?, ZIGLIO Frediano, 03/03/2003

Archive powered by MHonArc 2.6.24.

Top of Page