From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Michael Nolan <htfoot(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Declaring a field that is also an out parameter in a function |
Date: | 2024-07-07 14:53:24 |
Message-ID: | CAFj8pRDTn1GOy+QZGqUOrtyZHGfENNQTyBi-f8qesZ0JjXqPSg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
ne 7. 7. 2024 v 16:48 odesílatel Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
napsal:
> On 7/7/24 07:42, Pavel Stehule wrote:
> > I'm not sure why there's a warning about using an alias. 43.3.1 says
> > to use them for improved readability.
> >
> >
> > it is obsolete - aliases were used when Postgres doesn't support named
> > arguments.
>
> Is that was what it was complaining about or the fact they where
> declared and never used?
>
I am not sure if I understand the question. My reply was related to
generic usage of aliases.
Report from plpgsql_check was correct - and related variables were not
used.
> >
> > I don't know any good reason why one variable can use more than one
> name.
>
> Section 43.3.2. ALIAS provides the pros/cons.
>
> >
> > There can be an exception when argument names are very long, but
> > generally they are not used.
> >
> >
> >
> > Mike Nolan
> >
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2024-07-07 14:58:05 | Re: Declaring a field that is also an out parameter in a function |
Previous Message | Adrian Klaver | 2024-07-07 14:48:36 | Re: Declaring a field that is also an out parameter in a function |