FreeTDS Development Group

[Mark Schaal <mark AT champ.tstonramp.com>]

Oww, my brain hurts.  Has ANY big-endian machine ever run this?  I
currently believe that as long as the initial capabilities are set
then the database sends data in the correct byte-order, meaning that
the bitfiddling in tds_get_smallint() is bogus.  However, I changed
that and it makes things break in a different way that I haven't been
able to pinpoint.  My big fear is that somewhere there's a smallint or
an int that is byte-order dependent.

Enough for today.

Tally-ho,

Mark

> 
> 
> 
> On Thu, 26 Aug 1999, Michael Peppler wrote:
> 
> > OK - now on Solaris 7, Sparc...
> > 
> > I've made sure that HW_BIG_ENDIAN is defined.
> > 
> > However, I get:
> > 
> > kiruna (10:33AM):123 > perl -Mblib t/main.t       
> > Using /u6/home/mpeppler/src/Sybase-dist/DBD-Sybase-0.19/blib
> > 1..12
> > ok 1
> > Switch: DBI-1.08 Switch by Tim Bunce, 1.08
> > Available Drivers: ADO, ExampleP, Proxy, Sybase
> > Unknown property 7
> > ok 2
> > ok 3
> > ct_describe() failed at t/main.t line 61.
> > 3805:
> > Server message number=3805 severity=18 state=1 line=1 text=The token 
> > datastream length was not correct. This is an internal protocol error.
> 
> urgh, I have no idea on this one...Have any of the other Solaris people
> tried DBD::Sybase? Offhand, several of the token streams have a size in
> the first two bytes.  Looks like it didn't properly decide which one was
> the high order byte. Question is: which token caused it? And, if this is a
> server message, that means we sent it wrong and not the other way around.
> 
> Cheers,
> 
> 
> Brian


-- 
Mark J. Schaal                                  Phone:      (909) 620-7724
TST On Ramp                                     Fax:        (909) 620-8174
System Administrator                            E-Mail: mark AT tstonramp.com