Postgres Pro
Downloads
Home   >   mailing lists

Re: proposal: plpgsql, new check for extra_errors - strict_expr_check - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
Date
Msg-id CAFj8pRDOhjka18LDaZ9HBbBjoe31STHZcMF3DyzkOoeLSG23AQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql, new check for extra_errors - strict_expr_check  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
List pgsql-hackers
Tree view


ne 16. 6. 2024 v 16:43 odesílatel Marcos Pegoraro <marcos@f10.com.br> napsal:
Em dom., 16 de jun. de 2024 às 11:37, Pavel Stehule <pavel.stehule@gmail.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

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Using LibPq in TAP tests via FFI
Next
From: "David E. Wheeler"
Date:
Subject: Re: jsonpath: Missing regex_like && starts with Errors?