| From: | "Han" <zhouhanok(at)vip(dot)sina(dot)com> |
|---|---|
| To: | pgsql-odbc(at)postgresql(dot)org <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | SQL_C_CHAR & SQL_VARBINARY |
| Date: | 2002-11-26 04:22:39 |
| Message-ID: | 20021126042218.85AC7474E44@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi,
It seems that convertion between SQL_C_CHAR and SQL_VARBINARY in psqlodbc is not standard. For example, SQL_C_CHAR('01') should be explaned as hexdecimal and be converted to SQL_VARBINARY(00000001), but psqlodbc deals it the same as SQL_CHAR('01')--there are 2 ASCII chars inserted into the database. And vice versa, when retrived form database, SQL_VARBINAY('01') was convered to char string '01', but it should have been it's hex form.
If I was right, I hope a fix to it soon :)
Thanks!!!
Han
zhouhanok(at)vip(dot)sina(dot)com
2002-11-26
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2002-11-26 09:13:25 | Re: Bug #2 in latest ODBC driver (07.02.0004) |
| Previous Message | ALEX LORA | 2002-11-26 00:35:21 | a question |