| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>, Joel Jacobson <joel(at)trustly(dot)com> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-08 06:57:16 |
| Message-ID: | CAFj8pRASCYDKF4s6MV1EJrT3wkBd2DSpyP3rUX96Wrvi1tKo1A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>> Related to that, I suspect we could add better support to existing
>> commands for at least some of these things. For example, SELECT ... INTO
>> NOMULTI (instead of STRICT) to indicate that multiple rows are an error but
>> missing data is
>
>
> Another flag into NOMULTI can be solution too.
>
> The new syntax ":=" has some advantages:
>
> 1. it robust against type - it is harder to do unwanted swap of variables,
> and this mistake is very clear
>
should be "against typo", sorry
Pavel
> 2. the syntax ensure equality of target variables and source expressions.
>
>>
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2017-01-08 08:52:09 | Re: merging some features from plpgsql2 project |
| Previous Message | Pavel Stehule | 2017-01-08 06:56:17 | Re: merging some features from plpgsql2 project |