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

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

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

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

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

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

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

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

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


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> 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

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq