Skip site navigation (1) Skip section navigation (2)

Re: BUG #2917: spi_prepare doesn't accept typename aliases such as 'integer'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #2917: spi_prepare doesn't accept typename aliases such as 'integer'
Date: 2007-01-25 21:24:54
Message-ID: 6536.1169760294@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I dug into it a bit and found that pltcl and plpython appear to use 
> almost identical code, but only pltcl has this limitation documented. 
> I'm inclined to say we should document this for plperl and plpython for 
> stable releases and remove the limitation for all three for 8.3. I see 
> that SQL level prepare calls regprocin() to resolve type names, so maybe 
> we should that for the PLs when calling SPI_prepare as well. 

I think parseTypeString() may be the thing to use.  It's what plpgsql
uses...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-01-25 21:33:27
Subject: Re: BUG #2917: spi_prepare doesn't accept typename aliases
Previous:From: Tom LaneDate: 2007-01-25 21:20:43
Subject: Re: Implied Functional index use (redux)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group