Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL+ Beta bug?

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bo?ena Potempa" <Bozena(dot)Potempa(at)otc(dot)pl>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: PostgreSQL+ Beta bug?
Date: 2002-11-18 12:40:07
Message-ID: EKEJJICOHDIEMGPNIFIJKEEBJMAA.Inoue@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
> -----Original Message-----
> From: Bo?ena Potempa [mailto:Bozena(dot)Potempa(at)otc(dot)pl]
> 
> >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

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

In response to

Responses

pgsql-odbc by date

Next:From: Henshall, Stuart - Design & PrintDate: 2002-11-18 13:00:22
Subject: Re: Error when accessing from MSAccess95
Previous:From: Robert John ShepherdDate: 2002-11-18 11:31:56
Subject: Re: FATAL 1: Sorry, too many clients already

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group