FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

No!  The functionality is there, we just need to ensure a reasonable
textsize somehow.

Dumping packets from Query Analyzer reveals that it sends "SET TEXTSIZE
64512" just after login.

I think all we need to do is add "text size = 64512" in the [global] section
of our example freetds.conf.  Then we will always get a reasonable and
malloc()able size from the server, unless the user overrides this with
something unreasonable.  How does that sound?

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Wednesday, October 16, 2002 12:36 PM
To: TDS Development Group
Subject: [freetds] RE: freetds from cvs on cygwin - make check - 2 tes t fa
iled


Jim, 

There's a couple of issues with this.

1) I never fully figured out how this part of the protocol was supposed to
work. remember the bcp protocol in tds 7/8 is completely different from
4.2/5
2) when we read data from the host data file we malloc enough storage to
hold the data it's going to read. I work out how much to malloc by getting
the column size from the server. in sql 7/2000, the server tells me for
text/image I need 2Gb, which I merrily try and malloc. The holes in my logic
are obvious for all to see....

in essence then, its best to say that if the TDS protocol is 7 or 8 we
should say that this functionality is unavailable (for the time being
anyway)

Bill


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.