From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
---|---|
To: | Xtra Coder <xtracoder(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Any reasons for 'DO' statement not returning result? |
Date: | 2016-08-14 07:42:45 |
Message-ID: | CAKt_ZftVKBHRRG+RN8v49k+Qdk4XnYf-nC_ze-NOFUiL=O8QrA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If all you want is a temporary function, you *can* create it in the pg_temp
namespace though that seems hackish.
Maybe a better solution would be to extend CREATE FUNCTION in a way that
allows you to CREATE TEMPORARY FUNCTION?
On Sun, Aug 14, 2016 at 9:28 AM, Xtra Coder <xtracoder(at)gmail(dot)com> wrote:
> 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 discussions in previous years,
> i.e. topic was first stated more than 3 years ago)
> - most people agree that DO somehow needs to be made 'RETURNING', but
> there is no consensus how this should be made
>
> And out of that I feel there is no luck with that feature in foreseeable
> future :(.
>
>
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
From | Date | Subject | |
---|---|---|---|
Next Message | Xtra Coder | 2016-08-14 10:13:00 | Re: Any reasons for 'DO' statement not returning result? |
Previous Message | Xtra Coder | 2016-08-14 07:28:30 | Re: Any reasons for 'DO' statement not returning result? |