From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Prajval Poojari <ppoojari(at)erwin(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14545: Unable to retrieve parameter mode 'VARIADIC' |
Date: | 2017-02-14 23:17:41 |
Message-ID: | CAKFQuwbsr9fb1xiwfSQiOYOwenLqFYJH6ZhQjZLzCWBRFDQjUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Feb 14, 2017 at 4:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > I don't have access to an authoritative definition for what the allowed
> > values for information_schema.parameters.parameter_mode are.
>
> SQL2011 saith
>
> CONSTRAINT PARAMETER_MODE_CHECK
> CHECK (
> PARAMETER_MODE IN
> ( 'IN', 'OUT', 'INOUT' ) ),
>
>
> > The fact that our "VARIADIC" mode maps to "IN" on the information schema
> is
> > not accidental. The question is whether it is out-of-date.
>
> Not that I can see. SQL doesn't have VARIADIC, so there's no way to
> represent that a parameter is variadic within the information_schema.
>
Yeah, that is covered indirectly by:
"A CREATE FUNCTION command is defined in SQL:1999 and later. The
PostgreSQL version is similar but not fully compatible."
https://www.postgresql.org/docs/9.5/static/sql-createfunction.html
But VARIADIC is not specifically mentioned as being non-standard anywhere I
stumbled across so getting a definitive answer from the docs wasn't
possible.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | kcwitt | 2017-02-15 09:14:08 | BUG #14546: "point" type does not work with "IS DISTINCT" |
Previous Message | Tom Lane | 2017-02-14 23:10:53 | Re: BUG #14545: Unable to retrieve parameter mode 'VARIADIC' |