Re: BUG #3428: plperl spi_exec_prepared char length always unity - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #3428: plperl spi_exec_prepared char length always unity
Date
Msg-id 19328.1183657510@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #3428: plperl spi_exec_prepared char length always unity  (Matt Taylor <matt@lindenelevator.com>)
List pgsql-bugs
Matt Taylor <matt@lindenelevator.com> writes:
> On Thu, 2007-07-05 at 00:13 -0400, Tom Lane wrote:
>> IIRC, "char" means "char(1)" by default, so I'm unconvinced that this
>> behavior is a bug.

> Since 'character' is not accepted as a valid type by spi_prepare, is
> this bug a duplicate of BUG #2917?  Maybe I am just doing this wrong,
> the documentation is sparse.

Oh, duh, I should have thought harder.  Yeah, in 8.2 you will get the
internal 1-byte-char datatype, not bpchar which is what spi_prepare
will interpret this as meaning in 8.3 and beyond.

I'd suggest using "bpchar", or maybe better "varchar" (do you actually
want fixed-width char type??) for the time being.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Matt Taylor
Date:
Subject: Re: BUG #3428: plperl spi_exec_prepared char length always unity
Next
From: "James White"
Date:
Subject: BUG #3429: table named MULTIPOLYGON