From: | "Bo?ena Potempa" <Bozena(dot)Potempa(at)otc(dot)pl> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL+ Beta bug? |
Date: | 2002-11-18 09:34:52 |
Message-ID: | MKEIIFDEFPOPHIPFIFJCIEEIDHAA.Bozena.Potempa@otc.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
>From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
>Sent: Saturday, November 16, 2002 12:38 AM
[..]
>As long as you are using text(char or varchar) type, you can't
>store strings other than null terminated ones.
>Please use BYTEA type instead and bind the parameter using
>SQL_C_BINARY and SQL_VARBINARY.
But that's true only in ODBC, so I think it _is_ a bug
in ODBC driver. It is perfectly possible to store 0 in
varchar or char fields. Please try from psql:
INSERT INTO t values (chr(0)||chr(1)||chr(0));
and then check:
select ascii(substring(fc,1,1)) from t; - 0
select ascii(substring(fc,2,1)) from t; - 1
select ascii(substring(fc,3,1)) from t; - 0
Works perfect!
What do you think about this?
Best reagards,
Bozena Potempa
From | Date | Subject | |
---|---|---|---|
Next Message | Robert John Shepherd | 2002-11-18 11:31:56 | Re: FATAL 1: Sorry, too many clients already |
Previous Message | Han | 2002-11-18 07:41:05 | what's the latest protocol version? |