Skip to Content.
Sympa Menu

freetds - RE: DBLIB Unit Tests failing again

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Varley, David(CBorn at Alcoa)" <David.Varley AT alcoa.com.au>
  • To: 'TDS Development Group' <freetds AT franklin.oit.unc.edu>
  • Subject: RE: DBLIB Unit Tests failing again
  • Date: Sat, 14 Sep 2002 06:47:29 +0800




> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> Sent: Saturday, 14 September 2002 5:43 AM
> To: TDS Development Group
> Subject: [freetds] RE: DBLIB Unit Tests failing again
>
>
> > From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> > Sent: September 13, 2002 3:26 PM
> >
> > However, I do not recommend using TDS protocol 4.2 for any
> of the bcp
> > functions.
> > It doesn't work, as explained in the manual page for freebcp.
> >
> > The reason is that the bcp protocol differs radically from
> > Sybase to SQL
> > server 7/2000, so you have to use a TDS version that directs
> > the software
> > which method to use. 4.2 is ambiguous in this sense.
>
> Perhaps until 4.2 works, bcp_init should return an error if 4.2 is the
> protocol version. Why try to support 4.2, especially for something as
> esoteric as bcp, if 5.0 and 7.0 are known to work?
>
> --jkl

My concern was primarily that "make check" could successfully complete,
as a way to validate operation of CVS head code on different platforms.
If the dblib tests fail the ODBC tests never even get to run.
I changed the test DB from JDBC to a local MSQL one when JDBC wasn't
working, plus its much faster to test locally.
Default freetds.conf (which keeps popping up in new locations :) has
tds version = 4.2 I hadn't looked at the bcp manual or even known that
was what was being tested until the problems started!

Stopping a known-bad configuration crashing the server seems a good start,
be nice if it gave a warning and still passed the test so others could run
though. The incorrect data returned from MSQL should be a fail still.

Jim, I'd be happy for you to use a test SQLServer DB here, but there's be a
bit of hacking involved, starting with setting up a Dynamic DNS so you could
locate us (I've started on this), port-forwarding on the firewall to the
Server, and then the problems that I'll need to restart the Server when
FreeTDS crashes it, and I'm going away for a week in a week.

David




Archive powered by MHonArc 2.6.24.

Top of Page