FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> 
> Hey folks,
> 
> We're porting some code from windows to run against unixODBC and  
> FreeTDS and we need to use the following functions that are 
> currently  
> marked as stubs in http://freetds.org/api_status.txt:
> 
>    SQLDescribeParam
>    SQLDisconnect
>    SQLPutData
>    SQLSetEnvAttr
>    SQLCancel
>    SQLParamData
> 
> I'm wondering if someone could fill in the details on why they are  
> currently stubs and on what needs to be done to get them to "OK"  
> status, or alternatively, if there is a suggested workaround 
> we can use.
> 

This list is quite ouf of date. Check it at 
http://freetds.cvs.sourceforge.net/*checkout*/freetds/freetds/doc/api_st
atus.txt
SQLSetEnvAttr is "partial" in the meaning that it do not support not
zero-terminated string. But this is hardly your problem (I don't think
you are using Cobol or similar). SQLCancel work but is not thread-safe.
SQLDescribeParam require sql parsing (if you are not using Sybase
server). Other mentioned functions are implemented.

> If it's not something that requires uber-deep understanding of TDS,  
> OmniTI are prepared to do the work to implement those functions and  
> contribute the result back to the community.  If it proves to 
> be "too  
> hard" for us to implement, we'll consider compensating someone from  
> the FreeTDS development team to get it done--we see value in making  
> FreeTDS better and would rather spend money on that than on a closed  
> commercial solution.
> 
> Many thanks in advance for your attention,
> 
> --Wez.
> 
> -- 
> Wez Furlong
> Lead Architect
> OmniTI, Inc.
> tel: 410 872 4910 x 211
> 

Regards
  Frediano Ziglio