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

From Matt Taylor
Subject Re: BUG #3428: plperl spi_exec_prepared char length always unity
Date
Msg-id 1183655793.5299.12.camel@deb-matt.zipper.azi
Whole thread Raw
In response to Re: BUG #3428: plperl spi_exec_prepared char length always unity  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #3428: plperl spi_exec_prepared char length always unity  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, 2007-07-05 at 00:13 -0400, Tom Lane wrote:
> "Matt Taylor" <matt@lindenelevator.com> writes:
> > The spi_prepare and spi_exec_prepared doesn't seem to properly handle fixed
> > character types.  Only the first character of a string is passed to the
> > database.
>
> IIRC, "char" means "char(1)" by default, so I'm unconvinced that this
> behavior is a bug.
>
>             regards, tom lane
>


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.

Matt

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3428: plperl spi_exec_prepared char length always unity
Next
From: Tom Lane
Date:
Subject: Re: BUG #3428: plperl spi_exec_prepared char length always unity