Skip to Content.
Sympa Menu

freetds - RE: [freetds] 0.61rc2 ready?

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] 0.61rc2 ready?
  • Date: Thu, 20 Feb 2003 15:59:29 -0500

> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> Sent: February 20, 2003 3:39 PM
> > From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> > Sent: February 20, 2003 3:27 PM
> > >
> > > I think we are ready for rc2...
> >
> > Forgotten, it passed all tests on
> > - Linux (RH7.2/Intel) with ASE 11.9.2.3 (TDS5)
> > - Linux (RH7.1/Intel) with MSSQL 7 (TDS7)
> > - Linux (RH7.1/Intel) with MSSQL 2000 (TDS8)
> > - HP/UX (10.20/sparc) with MSSQL 2000 (TDS8)
> > (I had problem with MSSQL7 server)
> >
> > It compile without severe warnings on
> > - gcc 3.2 (HP/UX)
> > - gcc 2.95 (Linux)
> > - msvc6 (ODBC)
> > - gcc 2.95 (ODBC, mingw32, project files and make will be merged on
> > 0.62)
>
> Thanks, Freddy.
>
> I'll add your tests to the announcement and post rc2 tonight.

Can I make any statement about rc2 wrt to AIX or Solaris or Other Big Endian
Client? Is anyone here using the 0.61 branch that way?

I'm also interested in people using 0.61rc[12] with DBD::Sybase, sybper,
PHP, sqsh, other ODBC clients. I know we don't work with Star Office yet :/
but there have been trouble reports with DBD::Sybase in particular. I'm not
sure they're fixed in rc2.

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