Skip site navigation (1) Skip section navigation (2)

Enable/disable trigger path

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: pgadmin-hackers(at)postgresql(dot)org
Cc: Dave Page <dpage(at)postgresql(dot)org>
Subject: Enable/disable trigger path
Date: 2007-01-16 08:05:59
Message-ID: 45AC8767.4050508@lelarge.info (view raw or flat)
Thread:
Lists: pgadmin-hackers
Hi all,

Here is my first patch to support enable/disable trigger. This
functionnality is available since release 8.1 of PostgreSQL. Im' not
really happy with my code. I have some code to enable a trigger and some
code to disable it. I think it would be better to merge them since they
are pretty close. For example, I use two menus (Enable trigger and
Disable trigger). It would be better to use just one but I don't know
what to do :
 * rename the menu's title
 * use a checked menu.

Or perhaps two menus are just fine. Any advice on this ?

Also, I would like to add enable/disable all triggers but I don't know
where I should put the menu item : on the table name's contextual menu ?
on the "Triggers" contextual menu ?

Thanks for any tips on this matter.

Regards.


-- 
Guillaume.
<!-- http://abs.traduc.org/
     http://lfs.traduc.org/
     http://docs.postgresqlfr.org/ -->

Attachment: disabletrigger2.patch
Description: text/plain (4.9 KB)

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2007-01-16 08:39:11
Subject: Re: Enable/disable trigger path
Previous:From: Guillaume LelargeDate: 2007-01-16 07:55:17
Subject: Re: Roadmap

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group