freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Brian Bruns <brian.bruns AT gmail.com>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Which library to use with MS SQL
- Date: Tue, 23 Nov 2004 16:31:33 -0500
Not to make a sudden appearance and disagree with Jim, but it largely
depends on your requirements.
If your needs are moderate, and portability isn't an issue then I
agree that dblib is the most approachable API. But, I usually
recommend ODBC anyway these days, except when the performance overhead
of the driver manager is a problem (almost never), or when special
features like bulk copy are needed. You just never know when you
might be running another database in the future.
IMNSHO, ctlib gives you all the complexity of ODBC, with none of the
benefits, and is probably useful only for a) porting existing apps and
b) doing things not supported by dblib or ODBC (these exist in the
OpenClient ctlib, but I can't think of a single one that is true for
in FreeTDS).
All that said, the only wrong answer is libtds. ;-)
Brian
On Tue, 23 Nov 2004 15:30:04 -0500, Lowden, James K
<lowdenjk AT bernstein.com> wrote:
> > From: Ellen Spertus
> > Sent: Tuesday, November 23, 2004 2:35 PM
>
>
> >
> > I'm building an application that will be talking to Microsoft SQL
> > Server and am trying to decide which freetds library to use. I have a
> > working prototype that uses libtds, but the FAQ recommends using a
> > client library instead (http://freetds.org/faq.html#Which_API). When
> > considering dblib, I was spooked by the src/dblib/unittests/README
> > file, which says that, as of January 1999, t0003.c is broken. It
> > made me wonder if dblib and MS SQL do not, in fact, play well
> > together.
>
> Don't be spooked, Ellen. I think you'll find that t0003.c works fine
> these days (I know you will).
>
> IMO, db-lib is the easiest way to get going if you're starting from
> scratch. It's a matter of opinion, of course. ct-lib has fewer
> functions, but each one has many options. ODBC is more complicated to
> set up, and the extra layers of indirection (driver manager,
> generic-ness), make it harder to use.
>
> We provide db-lib documentation, as do both Microsoft and Sybase,
> online.
>
> HTH.
>
> --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.
> If you, as the intended recipient of this message, the purpose of which is
> to inform and update our clients, prospects and consultants of developments
> relating to our services and products, would not like to receive further
> e-mail correspondence from the sender, please "reply" to the sender
> indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New
> York, NY 10105.
>
>
>
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
-
[freetds] Which library to use with MS SQL,
Ellen Spertus, 11/23/2004
- <Possible follow-up(s)>
-
RE: [freetds] Which library to use with MS SQL,
Lowden, James K, 11/23/2004
- Re: [freetds] Which library to use with MS SQL, Brian Bruns, 11/23/2004
Archive powered by MHonArc 2.6.24.