FreeTDS Development Group

["Thompson, Bill D (London)" <ThompBil AT exchange.uk.ml.com>]

Nick,

I knew this rung a bell somewhere, and I just checked it.
It's not true to say that TDS 7/8 never sends an 0xAC token - it does.
I've just executed dblib/unittests/t0014 against a SQL 2000 database using
TDS 7
and that gets back a 0xac token - although freetds 0.60 doesn't recognise
it!

It gets this back after sending text data with dbwritetext, e.g.:

2002-10-09 05:24:44 in dbsqlok()
Received header @ 2002-10-09 05:24:44
0000  04 01 00 2f 00 34 01 00                           |.../.4..|


Received packet @ 2002-10-09 05:24:44
0000  ac 1b 00 04 74 00 78 00 74  00 73 00 01 a5 00 00   |....t.x.t .s.....|
0010  00 a5 08 00 08 00 54 49 4d  45 53 54 4d 50 fd 00   |......TIM ESTMP..|
0020  00 fc 00 00 00 00 00                              |.......|


2002-10-09 05:24:44 dbsqlok() marker is ac
2002-10-09 05:24:44 dbsqlok() found throwaway token
2002-10-09 05:24:44 inside tds_process_default_tokens() marker is ac
Unknown marker: 172(ac)!!


The plot thickens.....

Bill

> -----Original Message-----
> From: Castellano, Nicholas [SMTP:Nicholas_Castellano AT acml.com]
> Sent: Tuesday, October 08, 2002 8:47 PM
> To:   TDS Development Group
> Subject:      [freetds] Output parameters (src/dblib/unittests/t0022.c)
> 
> The behavior of output parameters in TDS 7/8 is different from TDS 4.2.
> In
> particular, it appears that output parameter results are not sent back to
> the client, so the test in src/dblib/unittests/t0022.c always fails.
> 
> I verified the behavior by sniffing the traffic from Query Analyzer to a
> SQL2K server over a TCP connection.  The packets we get back from the
> server
> appear identical to those we get when connecting from FreeTDS.  So I don't
> think it's something we're doing wrong; SQL Server just never sends a 0xAC
> token with the output parameters.  When TDS 4.2 is used to connect to the
> same server, the 0xAC packet is sent and the test succeeds.
> 
> I don't think it's good to include a test that may always fail in certain
> setups.  Is there some way we can limit this test so it doesn't execute
> for
> TSD7 and TDS8 connections?  Or should we just remove the test altogether?
> 
> Cheers,
> --nick
> 
> 
> The information contained in this transmission may contain privileged and
> confidential information and is intended only for the use of the person(s)
> named above.  If you are not the intended recipient, or an employee or
> agent
> responsible for delivering this message to the intended recipient, any
> review, dissemination, distribution or duplication of this communication
> is
> strictly prohibited. If you are not the intended recipient, please contact
> the sender immediately by reply e-mail and destroy all copies of the
> original message. Please note that for certain accounts we do not accept
> orders and/or instructions by e-mail, and for those accounts we will not
> be
> responsible for carrying out such orders and/or instructions. Kindly
> refrain
> from sending orders or instructions by e-mail unless you have confirmed
> that
> we accept such communications for your account. Please also note that to
> satisfy regulatory requirements we review the outgoing and incoming e-mail
> correspondence of staff members serving certain functions.
> 
> 
>     
>  << File: log.nts0090.42.txt >>  << File: log.nts0090.70.txt >>  << File:
> footer >>