Re: [pgAdmin][RM4842] trigger/compound trigger on a partitioned table
Hi Aditya
I have applied the patch and found one issue collection nodes are visible twice under the child node of the partition table. Please fix that.
On Wed, Dec 25, 2019 at 4:59 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
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 ToshniwalpgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune"Don't Complain about Heat, Plant a TREE"
Thanks & Regards
Akshay Joshi
Sr. Software Architect
EnterpriseDB Software India Private Limited
Mobile: +91 976-788-8246
Вложения
В списке pgadmin-hackers по дате отправления:
Предыдущее
От: Akshay JoshiДата:
Сообщение: Re: [pgAdmin][RM5024] Refactoring SQL of Functions and Procedures.
Следующее
От: Ganesh JaybhayДата:
Сообщение: [pgAdmin4][RM#5047] Add tab navigation for tabs under explain panelin query tool