Thanks, I'm aware about ability to create temp functions, but this is
actually too much overhead - I mean unneeded boilerplate code, but it seems
in current state it is "the least evil" which I have to use.
I think 'what i need' is support for following
- ability to switch session language from 's
Thanks for the link. After looking through it i see following major points:
- thread is from 2013 and nothing changed today in 2016
- quote from that thread (C) Dimitri Fontaine
"That topic apparently raises each year and rehash the same points"
(So ... there should be more similar discussio
ch case I do not need 'DO' at all
and this is simple. Probably PostgreSQL has another way to make that thing
simple.
On Fri, Aug 12, 2016 at 1:19 AM, Merlin Moncure wrote:
> On Mon, Aug 8, 2016 at 7:25 PM, Xtra Coder wrote:
> > Hi,
> >
> > I'm just curiou
Hi,
I'm just curious about the reasons of the design of 'DO' statement so that
it is not able to return result of the SELECT in its body.
References:
https://www.postgresql.org/docs/current/static/sql-do.html
http://stackoverflow.com/questions/14652477/how-to-perform-a-select-query-in-a-do-b
