RE: Read UNIVARCHAR field from Sybase 12.5.1

Yes and not. LONGBINARY coding is a bit different from IMAGE/TEXT. I
like Sybase coding. They use extensively usertype. LONGBINARY just tell
"wire is coded in such way" while usertype tells how to interpret this
type (binary, univarchar, etc). So future versions know how to skip
strange future data (like XML, composite column, etc).

An old patch sended in ML handle LONGBINARY/LONGCHAR.

freddy77

> 
> Hi Alex,
> 
> Until the introduction of this UNIVARCHAR Type, the only 
> datatype that had a varint size of 4 was a BLOB, i.e. TEXT 
> field. These always had the table name present.
> 
> We have to replace/add to  that test on varint_size with a 
> "is_blob_type" check....
> 
> bill
> 
> > -----Original Message-----
> > From:       Alex Kiesel [SMTP:kiesel@xxxxxxxxxx]
> > Sent:       20 November 2003 15:16
> > To: freetds@xxxxxxxxxxxxxxxxx
> > Subject:    [freetds] Read UNIVARCHAR field from Sybase 12.5.1
> > 
> > _______________________________________________
> > FreeTDS mailing list
> > FreeTDS@xxxxxxxxxxxxxxxxx 
> > http://lists.ibiblio.org/mailman/listinfo/freetds << 
> Message: Untitled 
> > Attachment >>
> 
> _______________________________________________
> FreeTDS mailing list
> FreeTDS@xxxxxxxxxxxxxxxxx 
> http://lists.ibiblio.org/mailman/listinfo/free> tds
>