FreeTDS Development Group

["Eric Deutsch" <edeutsch AT systemsbiology.org>]

Perhaps the maintainer of the FAQ could add the items brought up here to
the "Known Issues" section of the FAQ.  If we can assemble a list of
things that everyone agrees do not (yet) work, that might help folks
like Daniel.  Items that I know about:

1) Cannot fetch data from column of data type image from MSSQL2000
2) Cannot use dynamic SQL "place holders" [INSERT VALUES (?,?,?)]
3) Cannot connect to MSSQL using a Windows domain account

Obviously, if someone can provide examples for these or additional items
showing that they CAN work with FreeTDS, then maybe that will identify
some cases where they do and don't work for bug hunting.

One other item mentioned was "unable to get it to work with more than
one instance".  I think this needs more explanation.  I have in the past
been able to connect to the second instance on a MSSQL server (although
I didn't try to connect to the first and second instance simultaneously
if that's the issue).  If Nick can provide more details on this item,
maybe we can determine whether this is really not supported or just
doesn't work for him..

Thanks,
Eric



> -----Original Message-----
> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> Sent: Friday, March 08, 2002 8:52 AM
> To: TDS Development Group
> Subject: [freetds] RE: FreeTDS and MS SQL known issues
> 
> > From: Daniel Martin [mailto:dani AT online-canarias.com]
> > Sent: March 8, 2002 8:34 AM
> >
> > I am planning to use FreeTDS with MS SQL Server 2000 in a
> > project and I'd
> > like to know all the "bad news" about this combination,
> > before it was too
> > late. I'm looking for *all* possible errors and
> > incompatibilities
> 
> Daniel,
> 
> You'd like to know everything?  Wouldn't we all!
> 
> Seriously, there is no comprehensive list of what's not done or
doesn't
> work.  The FAQ and the User Guide are our best effort to describe the
> current state of affairs.
> 
> There isn't any problem specific to MS SQL Server 2000 that I know of.
> ISTR
> it might have new datatypes, which we don't support.  Using TDS 7.0,
> FreeTDS
> will appear as a SQL Server 7.0 client to your server.
> 
> How well FreeTDS will work for your project depends a little on your
data,
> somewhat on what software you'll be using with it, and quite a bit on
what
> aspects of the API you'll want.
> 
> My first try at documenting the API coverage can be found at:
> 
>
http://www.schemamania.org/freetds/cvs/freetds/doc/api_status.html
> 
> I think others on the list would agree that what is implemented works
> well,
> is both fast and stable.  When bugs are clearly identified, I have on
> occasion seen Brian fix them the same day.
> 
> HTH & regards,
> 
> --jkl
> 
> ---
> You are currently subscribed to freetds as:
[edeutsch AT systemsbiology.org]
> To unsubscribe, forward this message to leave-freetds-
> 127899P AT franklin.oit.unc.edu