Skip to Content.
Sympa Menu

freetds - RE: Strange things ...

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Strange things ...
  • Date: Fri, 15 Nov 2002 11:03:19 -0500


Let's not advertise output parameter support until we really have a handle
on the relevant MS SQL Server issues. Previously I have claimed that this
is an MS SQL bug, but now I'm not so sure.

Sybase docs say that passing output parameters back to the client is
deprecated, and only works when the relevant bit is flipped on in the
capabilities sent to the server (we're OK with Sybase servers, since we have
that bit set in the capabilities we send).

MS may have simply dropped support for this deprecated feature in SQL Server
7 SP3, or they may now require a capability bit requesting it. We don't
currently send any capabilities in our TDS7 login packet (I don't know if it
even has a concept analogous to Sybase capabilities.)

So, the jury is still out...it may be our fault, it may be MS's fault, and
in either case this is a deprecated feature that code really shouldn't be
counting on anyway!

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Friday, November 15, 2002 10:52 AM
To: TDS Development Group
Subject: [freetds] RE: Strange things ...

The next version (which we'll probably call 0.61) will include still more
fixes: output parameters of stored procedures


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.






Archive powered by MHonArc 2.6.24.

Top of Page