FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> 
> >
> > Mmmm.... 0xAF... this is TDS_LONGCHAR !!!
> > But we probably handle it as a XSYBCHAR.. which is not even  
> > supported by
> > Sybase!!
> > How is name column declared??
> 
> ciao freddy,
> 
> it's "varchar(40)"
> 
> here is the sql:
> 
> create table omq_sequences (name varchar(40) not null, id 
> decimal(14)  
> not null)
> alter table omq_sequences add constraint pk_omq_sequences 
> primary key  
> (name)
> go
> 
> if I change the connection encoding to "iso_1" then I get  
> datatype=CS_CHAR_TYPE (0) and usertype=2 back from ct_describe().
> 
>  From Sybase's ct-lib I get datatype=CS_LONGCHAR_TYPE (2) and  
> usertype=2 from ct_describe()
> 
> ciao
> david
> 
> ps grazie in anticipo per qualsiasi aiuto puoi offrire!
> 

Fixed in CVS HEAD.
Sybase 15 use LONGCHAR type for varchar when it have to convert to utf8.
This type use the same constant of a mssql type but have different
encoding. libTDS handled the two type in the same way so the error...
I'm doing more research for Sybase 15. It seems that it has some problem
with characters conversion and bcp...

freddy77