From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin4][Patch]: RM #4362 trigger function create script |
Date: | 2019-06-19 15:17:01 |
Message-ID: | CANxoLDfhrEn1E-ovPK6C-7Ra0Rd2QwpHktUmAAoN1fG_cr+GFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Dave
On Wed, 19 Jun, 2019, 19:57 Dave Page, <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Wed, Jun 19, 2019 at 9:55 AM Akshay Joshi <
> akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
>
>> Hi Hackers,
>>
>> Attached is the patch to fix RM #4362 trigger function create script.
>> Please review it.
>>
>
> While I can see how this works, I question why we have the string "SETOF"
> in prorettypname anyway? That's a separate property, so it should be in a
> separate variable. What if I have a type called "SETOFDavesStuff"
> (unlikely, but it illustrates the point)?
>
We have used pg_get_function_result(func_oid) to get the returns clause
for function and assign its value to prorettypename variable. I have
followed the same logic for trigger function and fixed it. Similar logic
has already been used for functions.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Yosry Muhammad | 2019-06-19 20:49:45 | Re: [GSoC][Patch] Automatic Mode Detection V1 |
Previous Message | Dave Page | 2019-06-19 14:27:46 | Re: [pgAdmin4][Patch]: RM #4362 trigger function create script |