FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

You're right, I don't know why I thought it was executing a stored proc
there...perhaps I'm as confused as Microsoft...

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Thursday, October 03, 2002 11:55 AM
To: TDS Development Group
Subject: [freetds] RE: Could someone try out something for me ?


Thanks for the verification nick,

surely there is something unusual about getting a stored procedure return
status when we haven't executed a stored procedure... I suppose SQL server
has executed a stored procedure internally to process the query, and is
sending us the status of that.

You're correct, the code currently handles this OK, but only by NOT handling
it if you see what I mean....

I'm getting ct_results() up to spec , which means that I'm obliged to return
control to the calling program, with a CS_STATUS_RESULT result type, when I
receive this message from the server...t0004 doesn't expect to receive it,
so with my ct-lib code, it fails....

see the manual page for ct_results(), if you want to understand more...it's
VERY different from dbresults() !

Bill

> -----Original Message-----
> From: Castellano, Nicholas [SMTP:Nicholas_Castellano AT acml.com]
> Sent: Thursday, October 03, 2002 4:42 PM
> To:   TDS Development Group
> Subject:      [freetds] RE: Could someone try out something for me ?
> 
> I see the same results as you, but 0x79 seems to be the token for a 
> stored procedure return status.  So I don't see anything unusual or 
> incorrect about the fact that the server sends you that token, or in 
> the way it is currently
> handled by FreeTDS.
> 
> Cheers,
> --nick
> 
> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> Sent: Thursday, October 03, 2002 11:26 AM
> To: TDS Development Group
> Subject: [freetds] Could someone try out something for me ?
> 
> 
> Hi all,
> 
> I'm getting some results from some tests that I don't understand.
> 
> I'm running ctlib/unittests/t0004 against a SQL server 2000 database 
> using TDS protocol version 7.0.
> 
> part of the tdsdump output ( you'll need to put turn this on for the 
> program
> ) shows the following exchange :
> 
> 0000  01 01 00 4a 00 00 01 00 53  00 45 00 4c 00 45 00   |...J....S
> .E.L.E.|
> 0010  43 00 54 00 20 00 2a 00 20  00 46 00 52 00 4f 00   |C.T. .*. 
> .F.R.O.|
> 0020  4d 00 20 00 23 00 74 00 30  00 30 00 30 00 34 00   |M. .#.t.0
> .0.0.4.|
> 0030  20 00 57 00 48 00 45 00 52  00 45 00 20 00 69 00   | .W.H.E.R .E.
> .i.|
> 0040  64 00 20 00 3d 00 20 00 31  00                     |d. .=. .1 .|
> 
> 
> 2002-10-03 16:05:00 ct_send() succeeded
> 2002-10-03 16:05:00 inside ct_results()
> Received header @ 2002-10-03 16:05:00
> 0000  04 01 00 2a 00 44 01 00                           |...*.D..|
> 
> 
> Received packet @ 2002-10-03 16:05:00
> 0000  79 00 00 00 00 81 01 00 00  00 09 00 26 04 02 69   |y........
> ...&..i|
> 0010  00 64 00 d1 04 01 00 00 00  fd 10 00 c1 00 01 00   |.d.......
> .......|
> 0020  00 00                                             |..|
> 
> As you may be able to see, we send a statement :
> 
> "select * from #t0004 where id = 1"
> 
> and we receive back a packet of three messages with markers "0x79", 
> "0x81" and "0xd1" . These are , respectively , an RPC return status 
> (!!!), followed by the "results" message and the "row" message I would 
> expect.
> 
> I'm very puzzled by the RPC return status message, I haven't made an 
> RPC call!
> 
> Could someone else verify this behaviour. If it can be independently 
> verified, I'll have to cope with it in the code...
> 
> regards,
> 
> Bill
> 
> ---
> You are currently subscribed to freetds as: 
> [Nicholas_Castellano AT acml.com] To unsubscribe, forward this message to 
> $subst('Email.Unsub')
> 
> 
> 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.
> 
> 
> 
> ---
> You are currently subscribed to freetds as: 
> [thompbil AT exchange.uk.ml.com] To unsubscribe, forward this message to 
> $subst('Email.Unsub')


---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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.