FreeTDS Development Group

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

> From: Michael Peppler [mailto:mpeppler AT peppler.org]
> Sent: October 29, 2002 11:33 AM
> 

My take on FreeTDS's status of these areas....

> The cs_calc/cs_cmp routines are just stubs, so they won't 
> work. They are
> only used if you set the UseMoney, UseNumeric or UseDateTime 
> attributes.
> These are turned off by default, so you shouldn't hit this problem by
> accident.

Never discussed, as best I remember.  

> > t/cursor............Your vendor has not defined 
> Sybase::CTlib macro CS_CURSOR_DECLARE at t/cursor.t line 66
> > dubious
> 
> You'd hit this if you tried to use ct_cursor() and friends to open
> client-side cursors. I don't know of anyone who actually uses this
> feature...

If client-side cursors are ever implemented, I think it would be to support
ODBC first.  Then if someone cared to, there might be enough infrastructure
to bring them to the other APIs.  

> prepare.t tests for ct_dynamic() and friends (i.e. prepared statements
> with ?-style placeholders). FreeTDS doesn't support that yet.

In the wings.  Frediano is working on that, not alone.  If he meets with
success this fall, I'd expect placeholders to appear in the next release of
FreeTDS.  

> Tests 20-22 test async calls (dbpoll() and friends). Won't work with
> FreeTDS. No biggee.

Not on our radar AFAIK. 

> > t/money.............Msg 5701, Level 10, State 2
> > Server 'episun7', 
> >         Changed database context to 'ged'.
> > 
> > FAILED tests 2, 4-7, 9-13
> >         Failed 10/13 tests, 23.08% okay
> 
> Again - uses the UseMoney attribute to return CS_MONEY datatypes in
> native format and the dbmnyXXX() routines to perform 
> arithmetic on these
> values. I guess that the dbmnyXXX() routines haven't been implemented
> yet.

Quite true, no dbmny* support in FreeTDS.  Don't know why.  That is, I think
we have the requisite logic in libtds.  

Thanks for your comments, Michael.  Steven, are you on your way?  

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.