[pgAdmin][RM4842] trigger/compound trigger on a partitioned table

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: [pgAdmin][RM4842] trigger/compound trigger on a partitioned table
Date: 2019-12-25 11:29:11
Message-ID: CAM9w-_=yMF3y9bbYmZMOxcJUqjkmh_pRD8iUibAjZLNnqKMJ3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Hackers,

Attached is the patch to fix the issue where it was not possible to add
constraints, index, rules, triggers and compound triggers on child tables
of a partitioned table.
The problem was with URLs formed which also included parent table OID,
which was not needed. The code is changed to add "url_jump_after_node"
param to skip after a certain node, which will will skip all the value
between jump_after_node to the last node, excluding jump_after_node and the
last node. Partitioned table itself is a "table" and can be multilevel.

Kindly review.

--
Thanks and Regards,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"

Attachment Content-Type Size
RM4842.patch application/octet-stream 15.9 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Aditya Toshniwal 2019-12-27 06:13:13 Re: [pgAdmin][RM5017] Use cheroot as default production server
Previous Message Aditya Toshniwal 2019-12-24 07:30:20 [pgAdmin][RM5038] Select2 enhancement - Load items on demand (scroll)