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

From: songjinzhou <2903807914(at)qq(dot)com>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(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:39:00
Message-ID: tencent_487E96114E16B161F1966B04499C0413820A@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

songjinzhou(2903807914(at)qq(dot)com)

From: Pavel Stehule
Date: 2023-01-25 23:24
To: songjinzhou
CC: pgsql-hackers
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
Date: 2023-01-25 22:21
To: songjinzhou
CC: pgsql-hackers
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 Bruce Momjian 2023-01-25 15:40:50 Re: CREATE ROLE bug?
Previous Message gkokolatos 2023-01-25 15:37:12 Re: Add LZ4 compression in pg_dump