Re: JDBC Prepared Statement Bug

From: Dave Smith <dave(dot)smith(at)candata(dot)com>
To: Doug McNaught <doug(at)wireboard(dot)com>
Cc: Dave <dave(at)candata(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: JDBC Prepared Statement Bug
Date: 2002-03-14 16:12:49
Message-ID: 3C90CC01.20701@candata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Well it is actually coded as '\u0000' which is valid value for a
character type. The 'C' backend takes this as '\0' and and end of line
terminator.

Doug McNaught wrote:
> Dave <dave(at)candata(dot)com> writes:
>
>
>>I am trying to use a Prepared Statement that has a character type. The
>>value I am trying to use is '\0' and it is getting set with the
>>setObject method.
>
>
> '\0' is not a legal value for character types. You'll need to use the
> BYTEA type instead and quote it properly.
>
> -Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Carl van Tast 2002-03-14 16:35:00 Re: Select not using primary key index
Previous Message Andre Radke 2002-03-14 16:00:20 problem with array of boxes