FreeTDS Development Group

[Brian Bruns <camber AT umcc.ais.org>]

Ok, I've fixed varbinary types and tested it for the datasets that I have,
and both sqsh and DBD::Sybase seem to work ok.

I'm not totally sure its right (it compiled and ran the first
time....scary!).  Conversion from varbinary->string, binary->string,
varbinary->binary, and binary->varbinary should all work but I've only
tested varbinary->string, so give it a try and see if it helps.

Brian

On Thu, 2 Sep 1999, Brian Bruns wrote:

> 
> 
> On Thu, 2 Sep 1999, Mark Schaal wrote:
> 
> > > Hmm...I don't have timestamps to compare but varbinary seems to work 
> > > fine:
> > > 
> > [..deleted..]
> > > 
> > > I'll look further, but it does seem strange that sqsh and DBD::Sybase
> > > would return different values.
> > > 
> > > Brian
> > 
> > I've found two problems which may/may not be related. 
> > (1) SYBBINARY doesn't work.  That's a simple matter of adding a 
> >     case to tds_convert() to send binary to the varbinary function.
> Shouldn't affect timestamps, fixed it anyway though.
> 
> > (2) SYBVARBINARY isn't getting sent the correct column sizes.  I
> >     define a column as varbinary(4).
> >     Input:  0x4444          0x88888888
> >     Output: 0x44440000      0x88888888
> >     So the convert function is getting the column size and not the
> >     actual data size.
> Brown paper bag time for letting that one through! :(
> 
> Actually, varbinary has to be redone from the tds layer on up for this.
> Ack! 
> 
> > 
> > Since you're looking at it and I don't need binary support here, I'll
> > move on to something else.
> > 
> > Mark
> > -- 
> > Mark J. Schaal                                      Phone:      (909) 
> > 620-7724
> > TST On Ramp                                 Fax:        (909) 620-8174
> > System Administrator                                E-Mail: 
> > mark AT tstonramp.com
> >