Re: proposal: plpgsql, new check for extra_errors - strict_expr_check

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
Date: 2024-06-16 15:10:39
Message-ID: CAFj8pRDOhjka18LDaZ9HBbBjoe31STHZcMF3DyzkOoeLSG23AQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ne 16. 6. 2024 v 16:43 odesílatel Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
napsal:

> Em dom., 16 de jun. de 2024 às 11:37, Pavel Stehule <
> pavel(dot)stehule(at)gmail(dot)com> escreveu:
>
>>
>> What is the expected benefit? Generally PL/pgSQL has very strict syntax -
>> and using double semicolons makes no sense.
>>
>> exactly, makes no sense. That is because it should be ignored, right ?
> But ok, if this is a different issue, that´s fine.
>

I don't follow this idea - when it does not make sense, then why do you use
it? It can be a signal of some issue in your code.

The source code should not contain a code that should be ignored.

But I am not a authority - can be interesting if this is allowed in PL/SQL
or Ada

Regards

Pavel

> regards
> Marcos
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2024-06-16 15:52:23 Re: jsonpath: Missing regex_like && starts with Errors?
Previous Message Andrew Dunstan 2024-06-16 14:59:49 Re: Using LibPq in TAP tests via FFI