FreeTDS Development Group

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

> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: September 3, 2002 10:24 AM
> 
> Jim, I put some verbage in the troubleshooting section about 
> tsql, but I
> fear it is already out of date given Freddy's work on domains.  I'll
> finish up the general documentation for it today.

Sounds good.  

> I posted some stuff for compiling the Sybase python module, 
> i'd like to add that in too.

Funny, I think I remember seeing that, but it's not in the UG.  I'll check
my patches directory and mailboxes tonight.  

> There's the 0x0f cancel packet problem, i think should be fixed before
> 0.60final. 

I'm glad to hear you say that.   

>From what I can tell, the "else if (marker == 0)" was added to
tds_process_cancel to allow for the possibility that a dead socket returns
no bytes.  Removing that line would resurrect the "loop forever on dead
socket" bug.  It seems to me that anything expecting data from a socket has
to distinguish between a packet with no data and a socket with no
connection.  

For sure, we don't react to an 0x0f token intelligently; at best we ignore
it.  What should happen, I think: we should recognize the 0x0f as a cancel
acknowledgement and record it somewhere as a TDS state, even if we don't use
the information anywhere yet.  Then, having dealt with the 0x0f packet, we
keep looking for an 0x04 with the cancel bit set?  

> What is the status on conversion?  Any outstanding problems
> there? (money?).  

Fixed AFAIK.  Frediano fixed my major complaints on Friday.  Haven't re-run
my tests myself yet. 

> Is ODBC working with DBD::ODBC now? There was a 
> problem as I recall.  Others?

I don't plan to test ODBC.  

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