Thread: ddl triggers

Hi

I was wondering whether it will be useful to extend postgreSQL support 
to ddl triggers.
This may be useful for tracking and auditing purposes.

I am planning on prototyping this.
Would be interested to hear any comment.

Thanks

Barnali

Barnali <barnali@persistent.co.in> writes:
> I was wondering whether it will be useful to extend postgreSQL support 
> to ddl triggers.

This has been proposed and rejected before ... see the archives.
        regards, tom lane

Tom,

> > I was wondering whether it will be useful to extend postgreSQL support
> > to ddl triggers.
>
> This has been proposed and rejected before ... see the archives.

Eh?  I thought it was a TODO.

--Josh

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

Josh Berkus <josh@agliodbs.com> writes:
>>> I was wondering whether it will be useful to extend postgreSQL support
>>> to ddl triggers.
>> 
>> This has been proposed and rejected before ... see the archives.

> Eh?  I thought it was a TODO.

Or "see the TODO list" ... I was looking for some small evidence of
familiarity with the previous discussions ...
        regards, tom lane

On Tue, 2005-05-31 at 11:13 -0400, Tom Lane wrote:
> Barnali <barnali@persistent.co.in> writes:
> > I was wondering whether it will be useful to extend postgreSQL support 
> > to ddl triggers.
> 
> This has been proposed and rejected before ... see the archives.

Could we keep track of NOT TODO items also?

The list of ideas suggested but then rejected is growing longer and we
rely on people's memory to say what was rejected previously.

The question is where do you put this idea if you reject it? :-)

Best Regards, Simon Riggs

> Could we keep track of NOT TODO items also?
>
> The question is where do you put this idea if you reject it? :-)
>
And of course a link to the thread, or an explanation on why it was
rejected. That way if someone can solve the reason for reject it maybe
a new discussion can be made.

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)