From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
Subject: | Re: plperl arginfo |
Date: | 2010-10-28 15:39:31 |
Message-ID: | AANLkTik7aA+j2Bx3K9whNo74wgTuWQEmyeO8mSZchOpD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/10/28 Andrew Dunstan <andrew(at)dunslane(dot)net>:
> While we were discussing allowing generic record type arguments to plperl
> functions, Tom suggested that we should expose the type information about
> the record members to plperl. I think if we do that we should probably
> expand it somewhat to all arguments, so that for non-trigger functions, we'd
> have $_ARG_INFO while could look something like this:
>
> {
> names => ['arg1', undef, 'arg3' ] , # no name was supplied for arg2
> modes => ['in', 'in', 'in' ], # do we support anything other than IN ?
variadic
Pavel
> types => ['integer', 'text', { name => 'somecomposite', fields => [
> 'field1', 'field2' ], types => ['date', 'numeric' ] } ],
> }
>
> Maybe we should also pass in type Oid info, too.
>
> I don't think this would be terribly difficult to do.
>
> thoughts?
>
> cheers
>
> andrew
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-10-28 15:45:11 | Re: max_wal_senders must die |
Previous Message | Tom Lane | 2010-10-28 15:39:11 | Re: plperl arginfo |