FreeTDS Development Group

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

I think we should just scrap src/dblib/unittests/t0022.c.  It seems to be
the general consensus that this is obsolete functionality and just isn't
useful behavior anyway.  This test is a pain for other reasons (it requires
permission to create procedures, which makes it fail on many non-privileged
setups where it might otherwise succeed).  This means that the test fails in
the example configuration with Sybase's JDBC server, which I find to be an
annoyance.

Any objections to removing the test?

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Monday, November 18, 2002 6:15 PM
To: TDS Development Group
Subject: [freetds] RE: Output parameters (was: Strange things)


Hi all,

I have an explanation for the "output parameters" issue.

In TDS 4.2, there was no direct method or protocol for submitting remote
procedure calls to the server. the only way to do it was via an "exec"
statement sent as an ordinary piece of SQL. In TDS 4.2, if a stored
procedure call with output parameters was submitted in this way, then a
token stream was returned, indicating the vales of the output parameters.

In TDS 7.0, Microsoft introduced a message type for directly submitting
remote procedure calls to the server. If this is used, then the token stream
will be returned.

However, up until SQL server 7 service pack 3, SQL server continued to send
back the "return value" token streams under the old conditions. In 7.0 SP3
MS put this behaviour under a TDS version check - old drivers got the
returnvalue, new ones did not.

The upshot of this is that we'll have to implement the RPC message stream,
if we want to capture return parameters from stored procedures in TDS 7 or
8.

I can help with the specifics of the TDS 7 RPC message protocol if anyone
wants to get stuck in.

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 we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.