> -----Original Message-----
> From: Gavin Sherry [mailto:swm@linuxworld.com.au]
> Sent: 11 August 2002 17:01
> To: Tom Lane
> Cc: pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] CREATE OR REPLACE TRIGGER
>
>
> On Sun, 11 Aug 2002, Tom Lane wrote:
>
> > Gavin Sherry <swm@linuxworld.com.au> writes:
> > > From memory, I think some of the pgadmin guys jumped up and down
> > > about it for a while:
> > > http://fts.postgresql.org/db/mw/msg.html?mid=1353289.
> >
> > Hmm. I remember Poure asking repeatedly for CREATE OR
> REPLACE VIEW,
> > and that makes a lot of sense to me, because other things
> *can* depend
> > on a view. (Unfortunately, by the same token it's a lot harder to
> > do.)
>
> I know. I am finishing off the patch now.
>
> > The use-case for replacing a trigger is not visible to the
> naked eye.
>
> That's okay then. I should have thought about it harder.
It would be nice for pgAdmin 'cos we can then let users alter properties
of objects at will. Currently we have a mix of things that can and can't
be editted. We often get asked 'why can we do X but not Y in pgAdmin'
and then have to explain that it's a PostgreSQL that doesn't allow us to
do Y (at least not with some nasty client side hacks that can break
dependencies in many cases - admittedly not with a trigger).
The more things our users can tweak on the fly, the better imho.
Regards, Dave.