FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

These don't look that hard to do, as we are mostly there already.  I 
wrote a unittest and the start of some code to implement these, and 
hopefully can find some time to finish it tommorow.  My one concern is 
that there is no "row buffer" for parameters like there are for regrows, 
so we need to copy the data somewhere for dbretdata() to fetch it, and I 
haven't found any approach that I like yet.  The rest of the functions  
are trivial as they just need to copy from the existing tds->param_info 
structure and viola!

Brian

On Tue, 3 Sep 2002, Lowden, James K wrote:

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