freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Thompson, Bill D (London)" <bill_d_thompson AT ml.com>
- To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] small patches
- Date: Thu, 6 Nov 2003 11:42:48 -0000
Hi James,
With respect to the bcp question, from the looks of what christos is up to,
he's using ct-library.
As you know, the BCP functionality isn't in ct-library.....yet.
This isn't too difficult to achieve - 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'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 ?
Bill
> -----Original Message-----
> From: Lowden, James K [SMTP:LowdenJK AT bernstein.com]
> Sent: 05 November 2003 20:30
> To: 'FreeTDS Development Group'
> Subject: RE: [freetds] small patches
>
> > From: Christos Zoulas [mailto:christos AT zoulas.com]
> > Sent: November 5, 2003 2:07 PM
>
> Thanks for the patches, Christos!
>
> > 1. In c++ you cannot use cs_config() and typedef struct cs_config
>
> FreeTDS has been compiled by a few C++ compilers. I wonder why this never
> cropped up before.
>
> > 2. constify server name
>
> This raises a philosophical issue. Sybase's published description of,
> say,
> ct_connect doesn't specify any const parameters. Granted, that's
> old-fashioned. But we match them slavishly.
>
> Should we constify everything we can? Should there be a nonconst option
> in
> pursuit of --enable-sybase-compat? If we do that, should we convert all
> the
> stupid #defines to enums, as Bjarne intended?
>
> If it were up to me, I'd say "yes" to the above. Damn the torpedos,
> better
> code ahead, say I. But I'm betting others have more experience than I do
> with portability and compatibility. I'd like to hear from them first.
>
> > PS: BCP writes don't work?
>
> It does:
>
> $ freebcp testdb..systypes out systypes.txt -c -S$S -U$U -P$P
>
> Starting copy...
>
> firstrow = 0 row_of_query = 29 rows written 29
> 29 rows copied.
>
> What does the "create table" statement look like for your failed trial?
>
> --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.
>
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
-
[freetds] small patches,
Christos Zoulas, 11/05/2003
- [freetds] sp_tables (ODBC), Patrick Poncet, 11/05/2003
- <Possible follow-up(s)>
-
RE: [freetds] small patches,
Lowden, James K, 11/05/2003
- RE: [freetds] small patches, Christos Zoulas, 11/05/2003
- RE: [freetds] small patches, Castellano, Nicholas, 11/05/2003
- RE: [freetds] small patches, Thompson, Bill D (London), 11/06/2003
- RE: [freetds] small patches, Lowden, James K, 11/06/2003
Archive powered by MHonArc 2.6.24.