current CVS version won't connect to MSSQL 7
blob at saghill.com
Thu Feb 24 14:43:55 EST 2000
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
- Message handlers
- no debugging yet, but it simply isn't called in the test
- returns succeed, doesn't set reason.
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...
> -----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.
> You are currently subscribed to freetds as: blob at saghill.com
> To unsubscribe, forward this message to
More information about the FreeTDS