| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matt Taylor <matt(at)lindenelevator(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3428: plperl spi_exec_prepared char length always unity |
| Date: | 2007-07-05 17:45:10 |
| Message-ID: | 19328.1183657510@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Matt Taylor <matt(at)lindenelevator(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2007-07-05 20:22:17 | Re: BUG #3429: table named MULTIPOLYGON |
| Previous Message | James White | 2007-07-05 17:19:48 | BUG #3429: table named MULTIPOLYGON |