Re: Re: Support plpgsql multi-range in conditional control

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: songjinzhou <2903807914(at)qq(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: Support plpgsql multi-range in conditional control
Date: 2023-01-25 15:50:49
Message-ID: CAFj8pRBqSN1Dqw_oGtv-rMiHUVfLtuhv3uu27SpPV7eYCAeqCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

st 25. 1. 2023 v 16:39 odesílatel songjinzhou <2903807914(at)qq(dot)com> napsal:

> Hello, my personal understanding is that you can use multiple iterative
> controls (as a merge) in a fo loop, otherwise we can only separate these
> iterative controls, but in fact, they may do the same thing.
>

1. please, don't use top posting in this mailing list
https://en.wikipedia.org/wiki/Posting_styl

2. I understand the functionality, but I don't think there is a real
necessity to support this functionality. Not in this static form, and just
for integer type.

Postgres has a nice generic type "multirange". I can imagine some iterator
over the value of multirange, but I cannot imagine the necessity of a
richer iterator over just integer range. So the question is, what is the
real possible use case of this proposed functionality?

Regards

Pavel

>
> ------------------------------
> songjinzhou(2903807914(at)qq(dot)com)
>
>
> *From:* Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> *Date:* 2023-01-25 23:24
> *To:* songjinzhou <2903807914(at)qq(dot)com>
> *CC:* pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
> *Subject:* Re: Re: Support plpgsql multi-range in conditional control
> Hi
>
>
> st 25. 1. 2023 v 15:39 odesílatel songjinzhou <2903807914(at)qq(dot)com> napsal:
>
>> Hello, this is the target I refer to. At present, our patch supports this
>> usage, so I later thought of developing this patch.
>>
>>
>> ------------------------------
>> songjinzhou(2903807914(at)qq(dot)com)
>>
>>
>> *From:* Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
>> *Date:* 2023-01-25 22:21
>> *To:* songjinzhou <2903807914(at)qq(dot)com>
>> *CC:* pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
>> *Subject:* Re: Re: Support plpgsql multi-range in conditional control
>> Hi
>>
>>
> ok, I was wrong, PL/SQL supports this syntax. But what is the real use
> case? This is an example from the book.
>
> Regards
>
> Pavel
>
>
>> st 25. 1. 2023 v 15:18 odesílatel songjinzhou <2903807914(at)qq(dot)com> napsal:
>>
>>> Hello, this usage scenario is from Oracle's PL/SQL language (I have been
>>> doing the function development of PL/SQL language for some time). I think
>>> this patch is very practical and will expand our for loop scenario. In
>>> short, I look forward to your
>>>
>>
>> I don't see any real usage. PL/SQL doesn't support proposed syntax.
>>
>> Regards
>>
>> Pavel
>>
>>
>>
>>> reply.
>>>
>>> Happy Chinese New Year!
>>>
>>> ------------------------------
>>> songjinzhou(2903807914(at)qq(dot)com)
>>>
>>>
>>> Maybe you didn't understand my reply. Without some significant real use
>>> case, I am strongly against the proposed feature and merging your patch to
>>> upstream. I don't see any reason to enhance language with this feature.
>>>
>>> Regards
>>>
>>> Pavel
>>>
>>>
>>>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2023-01-25 15:51:33 Re: New strategies for freezing, advancing relfrozenxid early
Previous Message Israel Barth Rubio 2023-01-25 15:46:55 Re: Authentication fails for md5 connections if ~/.postgresql/postgresql.{crt and key} exist