FreeTDS Development Group

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

What have we learned today?

1. dbcancel & Co. are fixed, thanks to Brian.

2. There is a uniqueidentifier patch ready for DBD::Sybase, but until then
it won't handle that datatype.  Need UG update on that.

3. tds_convert() shouldn't issue an error for anticipated zero-length
conversions.

4. Todo needs updating.  (So does ChangeLog).  

5. Bad uniqueidentifier handling in sqsh is probably due to sqsh not
understanding the datatype.  

6. Eric experienced problems with DBD::ODBC.  I consider that acceptable for
0.60.  Nothing personal, 
Eric!  :)  I don't want to hold up the release for a problem that might take
a while to isolate.  If OTOH it is isolated and can be fixed quickly, then
of course we should include the fix.  

Brian alleged "spurious conversion errors".  Anything specific/confirmed?

No new bugs.  Is good.  Expect -rc1 on Thursday or Friday if all stays quiet
on the western front. 

--jkl

> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: September 4, 2002 11:53 AM
> 
> a couple of other points.  We should mark as done:
> 
> . Someone broke early binding in ODBC
> . Add missing constants needed for python and verify working
> . Make pool configuration a non-recompile process
> . Add support for TDS 8.0 (login works)
> 
> and move the stuff that's done to somewhere else.
> 


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.