FreeTDS Development Group

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

> From: Savitri Sarangi [mailto:ssarangi AT Satyam.odc.ml.com]
> Sent: September 3, 2002 11:22 AM
> 
> We are using FreeTDS to connect from Unix C++ to SQL Server 2000. 

Welcome to the project, Savitri.   

> We notice that some dblibrary functions have 
> null implementation. At the
> moment we have come across

> char *dbretname(DBPROCESS *dbproc, int retnum)
> BYTE *dbretdata(DBPROCESS *dbproc, int retnum)
> int dbretlen(DBPROCESS *dbproc, int retnum)
> int dbnumrets(DBPROCESS *dbproc)

> Are they implemented in the next version? Can you give me an 
> update? 

They are not implemented, and no one is working on them.  I do not know if
their underlying data are extracted by the TDS layer.  

> Are there any more such functions? To be very frank, we have 
> assumed that all
> defined functions will be implemented as well. Since the function
> repeatedly failed, we looked at the source code and figured this out

http://www.freetds.org/api_status.txt

is a fairly recent attempt to document the status of the implementation.  

Recent snapshots log unimplemented functions.  We have discussed stricter
handling (return FAIL, for example), but have not implemented it as a
compile-time option.  

HTH.

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