FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> Sent: November 15, 2002 11:03 AM
> 
> Let's not advertise output parameter support until we really 
> have a handle on the relevant MS SQL Server issues.  

OK.

> Previously I have claimed that this
> is an MS SQL bug, but now I'm not so sure.

I lost track of this.  I remember that you bumped in to problems with some
versions of the server, but I thought it works in most cases.  

> Sybase docs say that passing output parameters back to the client is
> deprecated

I hadn't heard that before.  There's no mention of deprecation on the
dbretname page.  

http://manuals.sybase.com/onlinebooks/group-cn/cng1250e/dblib/@Generic__Book
TextView/32182;pt=3840/*#X

and in fact "deprecate" doesn't appear anywhere in Sybase's current db-lib
documentation.  

> 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.  

What does "capability" mean in TDS 7.0?  

I'm sure dbretname and friends work with any of Microsoft's servers with
their libraries.  I could give you a tcpdump trace if you send me your test
program and tell me what server to use.  but you already did that, right?  

Bill Thompson might be able to shed some light on this too, if we're
specific.  

> 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!

I think it's our fault unless we can show that their libraries fail to
convey output parameters back to the client.  I'm from Missouri wrt
deprecated. 

Regards, 

--jkl


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.