From: | Ryan Bradetich <rbradetich(at)uswest(dot)net> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: a couple of minor itches: RI Trigger Names, and |
Date: | 2002-05-08 01:42:04 |
Message-ID: | 1020822124.17204.14.camel@beavis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joe,
Thanks for the link. Didn't think to check the patches list :( I found
and downloaded the patch, but the patch does not apply cleanly (it
depends on some new files that are not present yet like:
src/backend/commands/tablecmds.c
)
But from what I have read, and the examples you gave this will do
exactly what I want :) not automatic, but still gives me the ability to
rename the trigger to something more obvious!
I'll have to play around with this some more and see if I can get it to
apply... or just wait until 7.2.2 comes out :)
Thanks for the excellent patch and pointer!
- Ryan
On Mon, 2002-05-06 at 14:22, Joe Conway wrote:
> Ryan Bradetich wrote:
> > Can anyone think of side-affects of changing the tgname column in
> > the pg_trigger system table? Does this proposal seem like an
> > acceptable solution? Would there be interest in this if I provided
> > a patch to do this?
>
> FWIW, not exactly what you are proposing, but ALTER TRIGGER RENAME is
> available in current CVS. See:
> http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-altertrigger.html
>
> Joe
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-05-08 01:57:23 | Re: OK, lets talk portability. |
Previous Message | jade | 2002-05-07 22:36:30 | postgresql 7.1 file descriptor |