Re: PostgreSQL+ Beta bug? - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: PostgreSQL+ Beta bug?
Date
Msg-id EKEJJICOHDIEMGPNIFIJKEEBJMAA.Inoue@tpf.co.jp
Whole thread Raw
In response to PostgreSQL+ Beta bug?  (Bożena Potempa <Bozena.Potempa@otc.pl>)
Responses Re: PostgreSQL+ Beta bug?
List pgsql-odbc
> -----Original Message-----
> From: Bo?ena Potempa [mailto:Bozena.Potempa@otc.pl]
>
> >From: Hiroshi Inoue [mailto:Inoue@tpf.co.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

Which version of PostgreSQL server are you connecting ?

Here I see all 0 i.e.

  select ascii(substring(fc,1,1)) from t; - 0
  select ascii(substring(fc,2,1)) from t; - 0
  select ascii(substring(fc,3,1)) from t; - 0

regards,
Hiroshi Inoue

pgsql-odbc by date:

Previous
From: "Robert John Shepherd"
Date:
Subject: Re: FATAL 1: Sorry, too many clients already
Next
From: "Henshall, Stuart - Design & Print"
Date:
Subject: Re: Error when accessing from MSAccess95