FreeTDS Development Group

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

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: April 11, 2003 2:48 PM
> 
> Well there are some things todo IMHO before 0.62 see the light.

These all sound good to me.  

> Charset handling
> - conversion for Sybase
> - conversion for different coding in tds7/tds8 (every 
> different columns)

Absolutely.  

> - test variable-byte (utf8/big5)

Yes.  Except I don't know if we have to handle stateful encodings.  If your
algorithm is ready for prime time, OK.  

> - test all string length computation and rewrite some code (many code
> assume fixed character conversions)

Much also assumes the first zero byte terminates a string...  And many OS's
don't provide a wide-character equivalent of strlen() et. al.  Makes me wish
for C++ and STL and basic_string<>, but I think we're going to get away with
pointer-to-buffer + count-of-bytes.  

> RPC (I started this work but many things don't still work)
> - finish tests under ctlib (they do not check wrong returned 
> values...)
> - fix ctlib too

Bill is going to continue to send us ct-lib fixes/enhancements.  

I would be happy if 0.62 had *just* any-to-any encodings.  Better RPC would
be nice, too; I might even work on TDS 5.0 RPC packets.  I think client-side
UTF-8 is very important, because of RH8, and I would suggest we cut a
release sooner than later if that becomes a pressing issue.  

> - SQLGetInfo

All of SQLGetInfo?  Or just just what's in TODO?

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.