Skip to Content.
Sympa Menu

freetds - RE: [freetds] small patches

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] small patches
  • Date: Thu, 6 Nov 2003 10:44:08 -0500

> From: Thompson, Bill D (London) [mailto:bill_d_thompson AT ml.com]
> Sent: November 6, 2003 6:43 AM
>
> the ct-library bcp functions map
> almost exactly to the db-library ones.
> but we need to move the code into a common library.
>
> I'd suggest we do it like convert - we have the bcp stuff in
> its own C file
> in the tds library, invoked from db-library and ct-library.
> Any header stuff could go in tds.h, or maybe its own header file...

I agree completely. It might be easiest to start by "mv dblib/bcp.c
tds/bulkcopy.c" and s/db/tds/. A lot of what's in that file is support
functions.

I wouldn't be surprised if the db-lib bcp functions could be written as
calls to the ct-lib ones. My guess is your tds/bcp.c interface will end up
looking a lot like the cs-blk API.

> I'll take this on, as part of my ct-library work.
>
> If you agree, could you create a stub C file in src/tds and
> do the necessary makefile/etc integration ?

Oh, absolutely! Who could turn down an offer like that? Look for it on
Monday.

> from the looks of what
> christos is up to, he's using ct-library.

He told me off-line he's using freebcp. I suspect a datatype problem.

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