> 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.
--
regard
On Tue, 2005-05-31 at 11:13 -0400, Tom Lane wrote:
> Barnali <[EMAIL PROTECTED]> 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
Josh Berkus 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
familiar
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
Barnali <[EMAIL PROTECTED]> 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)---
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)-
On Thu, 7 Oct 2004, David Fetter wrote:
> On Thu, Oct 07, 2004 at 11:47:55AM +0700, David Garamond wrote:
> > Joshua D. Drake wrote:
> > >>This brings up an interesting idea. What if it were possible to set
> > >>some kind of rules on DDL at database creation time? For example, I'd
> > >>like to
David Fetter <[EMAIL PROTECTED]> writes:
> How big a project would it be to have generalized DDL triggers? Apart
> from resource allocation, what are some downsides of providing such a
> facility?
BEFORE triggers on the system catalogs are Right Out. In principle we
could support AFTER triggers,
On Thu, Oct 07, 2004 at 11:47:55AM +0700, David Garamond wrote:
> Joshua D. Drake wrote:
> >>This brings up an interesting idea. What if it were possible to set
> >>some kind of rules on DDL at database creation time? For example, I'd
> >>like to be able to throw an error if somebody tries to nam
