freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Brian Bruns <camber AT umcc.ais.org>
- To: TDS Development Group <freetds AT franklin.oit.unc.edu>
- Subject: Re: current CVS version won't connect to MSSQL 7
- Date: Thu, 24 Feb 2000 19:13:40 -0500 (EST)
I really can't say what state sybperl is in. Most of the development and
testing revolve around sqsh/php/dbd::sybase so many things have changed
since the last time I tested with sybperl.
On Thu, 24 Feb 2000, Dave Blob wrote:
> Really? How much have you tested it? The reason I'm surprised is that the
> sybperl tests fail on the following:
>
> - a failed query: "select count(*) from systypes where"
> - My trivial debugging leads me to beleive this is because
> dbsqlexec returns true rather than reading the response packet and queueing
> it
dbsqlexec calls dbresults() which in turn calls
tds_process_result_tokens(), so at the protocol level we should know if it
worked or didn't before dbsqlexec() returns...I'll look into it more.
> - Message handlers
> - no debugging yet, but it simply isn't called in the test
again, should work...probably a small bug.
> - dbpoll
> - returns succeed, doesn't set reason.
dbpoll is not implemented.
>
> I would say the first two are critical pieces. As I noted before, I tried
> using sybperl anyhow, but to no avail - the sql function doesn't work,
> although the separate calls do - I haven't quite tracked that one down yet.
>
> Anyhow, all this isn't to be critical, I'd love to use this when it's
> working, and am stuck with using DBD::ODBC in the meantime. I just don't
> think it's fair to say it works great, when it's got a few things that are
> undone, and doesn't pass what are some pretty straightforward tests...
Have you tried using DBD::Sybase?
>
> Dave
>
> > -----Original Message-----
> > From: William.P.McGonigle AT artoo.hitchcock.org
> > [mailto:William.P.McGonigle AT artoo.hitchcock.org]
> > Sent: Thursday, February 24, 2000 1:27 PM
> > To: TDS Development Group
> > Subject: [freetds] Re: current CVS version won't connect to MSSQL 7
> >
> >
> > --- Brian Bruns wrote:
> > Eh, but isn't network order MSB (big endian) and sparc host
> > order would be
> > big endian as well, so no conversion would take place...i
> > think anyway....
> > But agreed, maybe we need htoms and mstoh ? :-)
> > --- end of quote ---
> >
> > Seems right on both accounts.
> >
> > BTW, I'm now using FreeTDS (last week's CVS)
> > --with-tdsver=4.2 against MSSQL 7 on Solaris 7 and everything
> > seems to be working perfectly
> > (apache/mod_perl/Apache::DBI/DBD::Sybase). The only thing
> > that suprised me was to find MSSQL errors in the apache error
> > log, and not in the TDS log.
> >
> > Great job, guys.
> >
> > -Bill
> >
-
Re: current CVS version won't connect to MSSQL 7
, (continued)
- Re: current CVS version won't connect to MSSQL 7, William P. McGonigle, 02/14/2000
- Re: current CVS version won't connect to MSSQL 7, William P. McGonigle, 02/18/2000
- Re: current CVS version won't connect to MSSQL 7, Brian Bruns, 02/18/2000
- Re: current CVS version won't connect to MSSQL 7, Ken Seymour, 02/18/2000
- Re: current CVS version won't connect to MSSQL 7, Brian Bruns, 02/18/2000
- Re: current CVS version won't connect to MSSQL 7, William P. McGonigle, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, Dave Blob, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, William P. McGonigle, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, Brian Bruns, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, richard, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, Brian Bruns, 02/24/2000
- Re: current CVS version won't connect to MSSQL 7, Michael Suedkamp, 01/29/2024
Archive powered by MHonArc 2.6.24.