From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Some questions about the array. |
Date: | 2015-11-09 13:53:48 |
Message-ID: | CAFj8pRDSCpmwwzc9KYTGhGLG8PGUJJUu_-Jk_-8nX-BXPFD+sQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-11-09 14:44 GMT+01:00 YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>:
> On Monday 09 November 2015 13:50:20 Pavel Stehule wrote:
> > New symbols increase a complexity of our code and our documentation.
> >
> > If some functionality can be implemented via functions without
> performance
> > impacts, we should not to create new operators or syntax - mainly for
> > corner use cases.
> >
> > Regards
> >
> > Pavel
>
> Ok we can use {:} instead [:] for zero array access.
> The function is the solution half.
>
It isn't solution. The any syntax/behave change have to have stronger
motivation. We had so talk about it 20 years ago :(
Regards
Pavel
>
> --
> YUriy Zhuravlev
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-11-09 13:58:18 | Re: proposal: PL/Pythonu - function ereport |
Previous Message | YUriy Zhuravlev | 2015-11-09 13:44:45 | Re: Some questions about the array. |