Re: RM-2519: Show the trigger function under the trigger node.

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: RM-2519: Show the trigger function under the trigger node.
Date: 2020-10-08 16:47:33
Message-ID: CANxoLDcgcya2cSO-axRTJwKnBV1DVTLUYJiiYTKR_6M+nC6amw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Thu, 8 Oct, 2020, 20:22 Dave Page, <dpage(at)pgadmin(dot)org> wrote:

> Hi Akshay,
>
> On Thu, Oct 8, 2020 at 3:43 PM Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
> wrote:
>
>> Hi Dave/Team
>>
>> I have started working on RM #2519 to show the trigger function under the
>> trigger node. I have made the changes to the code and the trigger function
>> is visible under the respective trigger node.
>>
>> Changes made to achieve this:
>>
>> - If the trigger function is in the same schema then it works
>> absolutely fine, the user can update the properties, view the SQL,
>> Statistics, Dependencies, and Dependents.
>> - If the trigger function is from the other schema then we need to
>> change the schema id as we have a strict API route which adds the schema id
>> where the trigger exists. Change has been done and it works.
>> - For the trigger function from the other schema, I have added the
>> schema-qualified name.
>> - Remove the menu options and add a dummy menu "No menu is available
>> for this object" when the user selects the trigger function under the
>> trigger node. Have to do this because of the different API routes, as the
>> object is not available and personally, I feel we should not show the
>> context menu to create, delete, drop from there.
>>
>> *Note:* To remove the menu option completely I have modified the
>> *menu.js* and check if the 'showMenu' function is defined. If it is
>> defined then call that function and based on the return value, will make
>> the decision.
>>
>> Please refer to the below screenshot for more clarity:
>> [image: 2519.png]
>>
>> Thought/Suggestion?
>>
>
> Yeah, we should not be able to create/drop there, as the trigger must have
> the function anyway (you can't define a trigger without a function in PG,
> nor can you drop a function that's being used by a trigger).
>
> However, we should have a working Properties option I would say.
>

Yes, it is working from properties tab. User can edit from there.

>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2020-10-09 06:23:05 pgAdmin 4 commit: Ensure that '.sql' extension is added when saving a f
Previous Message Dave Page 2020-10-08 14:52:27 Re: RM-2519: Show the trigger function under the trigger node.