Skip to Content.
Sympa Menu

freetds - RE: [freetds] TDS_DONE_TOKEN

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] TDS_DONE_TOKEN
  • Date: Wed, 30 Apr 2003 14:42:16 -0400

> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: April 30, 2003 12:01 PM
>
> I am pretty sure that after these changes, it will be
> possible to free the
> result structure(s) at the proper time, and not when a query
> is submitted.

You don't know how happy I am to hear you say that. I tripped on that in
dealing with TDSCOLINFO stuff in bcp.c.

> I was holding back on finishing these changes until James is
> finished and
> the code settles down a bit after the charset changes....

I hope to commit compilable, minimally working code this weekend, so we can
synch up. I think it's important to keep you informed of data structure and
header changes. I don't expect my other changes (e.g. in bcp.c) to matter
very much to you; I'm trying to make them transparent.

It's 90% done, so there's only 90% more to go, you know.

"minimally working" means unit tests work for ASCII and UTF-8 clients
against a TDS 7.0 server. Beyond that lies finding corner cases, which you
might as well be a part of. :-) Further down the road is UCS-2 clients
and/or UTF-8 servers, but these are both generalization problems. The data
structures we have now should (famous last words...) suffice.

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.





Archive powered by MHonArc 2.6.24.

Top of Page