From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Fixed PPAS trigger column view condition |
Date: | 2014-10-10 15:54:51 |
Message-ID: | CA+OCxow8Jb3BGdLhf8AYiHhm-89FayYzMfrqkJoW-hXqYPcbRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Oct 10, 2014 at 1:35 PM, Sanket Mehta
<sanket(dot)mehta(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> There is one issue with pgadmin while viewing the trigger definition created
> for PPAS server as below:
>
> CREATE OR REPLACE TRIGGER tr_a
> BEFORE UPDATE OF cl1 ON a FOR EACH ROW
> begin
> if(:new.cl1 < 0) then
> insert into a values (:new.*);
> END if;
> END;
>
> after creating the trigger using above query,column name cl1(highlighted
> part above) is not visible in property window for that trigger.
>
> In current implementation, there is a condition:
>
> GetLanguage() != wxT("edbspl") in
>
> ShowTreeDetail() and ReadColumnDetails() functions in pgTrigger.cpp file
> which will prevent it to fetch column name in case db server is PPAS.
>
> I have removed that condition and tested it. It works fine now.
> I have attached the same patch with this mail for your reference.
> Please review it and if it looks good to you please do the needful.
Are per-column triggers in PPAS something that's been added in a
recent release? I wonder if there should be a version check in there,
as the code was pretty clearly intended to be written as it is
originally.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2014-10-11 13:23:36 | Re: Fwd: Auto-complete and Calltips in SQL Editor |
Previous Message | Sanket Mehta | 2014-10-10 12:35:40 | Fixed PPAS trigger column view condition |