Re: BUG #2917: spi_prepare doesn't accept typename aliases - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: BUG #2917: spi_prepare doesn't accept typename aliases
Date
Msg-id 8C527078-0F5A-4EF9-8411-280B2E2611D7@decibel.org
Whole thread Raw
In response to Re: BUG #2917: spi_prepare doesn't accept typename aliases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #2917: spi_prepare doesn't accept typename aliases  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Jan 26, 2007, at 9:31 AM, Tom Lane wrote:
> If you wanted to be a bit more ambitious maybe you could change the  
> fact
> that this code is throwing away typmod, which means that declarations
> like "varchar(32)" would fail to work as expected.  Perhaps it  
> should be
> fixed to save the typmods alongside the typioparams and then pass them
> to InputFunctionCall instead of passing -1.  On the other hand, we  
> don't
> currently enforce typmod for any function input or result  
> arguments, so
> maybe it's consistent that spi_prepare arguments ignore typmods too.
> Thoughts?

I'd like to see us move towards supporting that; both for function  
parameters/results as well as inside functions. It'd be nice if both  
cases got fixed at once, but IMHO fixing only one now would be better  
than fixing none.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Proposal: Snapshot cloning
Next
From: Jim Nasby
Date:
Subject: Re: Proposal: Change of pg_trigger.tg_enabled and adding