Re: Problem about Bytea and SQL_C_CHAR

From: "Han" <zhouhanok(at)vip(dot)sina(dot)com>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-odbc(at)postgresql(dot)org <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Problem about Bytea and SQL_C_CHAR
Date: 2002-11-29 02:57:08
Message-ID: 20021129025637.65489475A1E@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hiroshi Inoue,

>Han wrote:
>>
>> Hiroshi Inoue,
>>
>> OK, that crash problem solved. But there are even more
>> datatype conversion problems.
>> First I prepared an insert statement, bound params all
>> using SQL_C_CHAR and SQL_NTS, and execute it. All type
>> of column values were inserted properly except bytea--
>> it's null in the column.
>
>OK please try the snapshot dll at http://w2422.nsk.ne.jp/~inoue/
>again.
It's OK now! Expect to CVS :)
>
>> And then I retrived data from the table I just
>> inserted, binding columns with SQL_C_DEFAULT. Most
>> colums returned wrong value.
>
>Hmm for example ? I don't have much time, sorry.
It's alright. My mistake, sorry!

Regards,

　　　　　　　　Han
　　　　　　　　zhouhanok(at)vip(dot)sina(dot)com
　　　　　　　　　　2002-11-29

Browse pgsql-odbc by date

  From Date Subject
Next Message Han 2002-11-29 03:13:17 out length err with SQL_TINYINT
Previous Message Jeff Eckermann 2002-11-29 02:45:19 Re: Can't get more than 255 chars out of memo field in Acc