Bug#500451: tdsodbc: transfer the last character to next field

2009-05-19 Thread Boris shtrasman
I found another thing , This problem arises only with Priority Systems (ESHbell) - Another way to work with it (Around it ) is to use FreeBidi and prevent nulls for instance if you change nulls to space (or -1 for instance ) where the null number should be set, After the input you should remove

Bug#500451: tdsodbc: transfer the last character to next field

2008-10-06 Thread ZIGLIO, Frediano, VF-IT
Solved, problem is due to charsets with a shift state where shift state was left into iconv. See patch http://freetds.cvs.sourceforge.net/viewvc/freetds/freetds/src/tds/iconv.c?view=patchr1=1. 132r2=1.132.2.1sortby=date. You should see an updated patch for 0.82 on freetds.sourceforge.net

Bug#500451: tdsodbc: transfer the last character to next field

2008-10-01 Thread ZIGLIO, Frediano, VF-IT
Problem is related to how FreeTDS use iconv and shift state. Last characters (I don't understand why) left in iconv as the shift state. Adding a tds_iconv(tds, char_conv, to_client, NULL, NULL, outbuf, outbytesleft); line before return in read_and_convert and removing assert for

Bug#500451: tdsodbc: transfer the last character to next field

2008-09-30 Thread ZIGLIO, Frediano, VF-IT
Well, these steps help reproduce the problem even with tsql utility 1 create table #tmp1 (i int, v varchar(10) collate Hebrew_CI_AI) 2 go 1 insert into #tmp1 values(1, cast(0xde05d905d305e205 as nvarchar(10))) 2 insert into #tmp1 values(2, cast(0x69006e0066006f00 as nvarchar(10))) 3 insert into