po 3. 6. 2024 v 18:46 odesílatel Erik Wienhold <ewie@ewie.name> napsal:
On 2024-06-03 00:18 +0200, Tom Lane wrote: > "David G. Johnston" <david.g.johnston@gmail.com> writes: > > I think you just wrote the equivalent of: > > l_cnt := (select 1 as delete from foo3 where id=1); > > Which is a valid query. > > Still another example of the folly of letting AS be optional. > I don't suppose we can ever undo that though.
How about inventing an opt-in strict mode (like in Perl or JavaScript) that prevents certain footguns? For example, disallowing bare column labels.
That could be enabled for the current session or transaction:
SET strict_parsing = { on | off };
Or just for individual routines:
CREATE PROCEDURE myproc() SET strict_parsing = { on | off } LANGUAGE plpgsql ...
Probably it is not bad idea - it can be generally useful
But I think it is better to introduce a new entry for plpgsql expressions in gram.y.
Unfortunately it is not a compatible change. Years ago was popular to use a pattern
