CREATE OR REPLACE VIEW / TRIGGER

Jean-Michel POURE wrote:
[Charset iso-8859-15 unsupported, filtering to ASCII...]

Dear community, dear friends,

I know it is feature freeze, so forgive me for this (ancien) question : would
it possible to add CREATE OR REPLACE VIEW and CREATE OR REPLACE TRIGGER in
current PostgreSQL 7.2 release? Otherwise, it will take another year before
these long-needed features are added.

Is this really a difficult hack?

If difficult or not doesn't matter. It is not the way we do
development in the PostgreSQL team.

We are right now in BETA5 and Release Candidate 1 is
scheduled for tomorrow. Plus v7.2 is overdue, long waited
for.

No chance, sorry. v7.2 will go out the door without these
features. But you are more than welcome to provide patches
for v7.3 that implement them.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Jean-Michel POURE <jm.poure@freesurf.fr> writes:

I know it is feature freeze, so forgive me for this (ancien) question : would
it possible to add CREATE OR REPLACE VIEW and CREATE OR REPLACE TRIGGER in
current PostgreSQL 7.2 release?

No. RC1 is *tomorrow*, and we're not pushing it back to add features.

Otherwise, it will take another year before
these long-needed features are added.

I'd like to ask people not to adopt the mindset that PG releases are a
year apart. I know it's been that way for the last two, but the project
goals are still to have a release every four-to-six months. If we go
into the development cycle with the notion that the next release is a
year out, it will be a self-fulfilling prophecy.

regards, tom lane

This brings up a question I have been meaning to ask....

RI constraints create triggers. You can't drop RI constraints, so if you re-create one that already exists you accidentally create duplicate RI triggers (or so it appears to my untrained hyperopic eyes).

Would this kind of functionality (whenever added) also affect creation of RI triggers? i.e. if I run

alter table scooby add constraint fk_scooby_scrappy foreign key (puppyid) references scrappy (scrappyid);

twice, I won't get twice as many RI triggers as I need? I would be happy either with this behaviour or the ability to alter table scooby drop constraint fk_scooby_scrappy (already in TODO I think). Just asking.

Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: iharding@tpchd.org

Tom Lane <tgl@sss.pgh.pa.us> 01/17/02 07:33AM >>>

Jean-Michel POURE <jm.poure@freesurf.fr> writes:

I know it is feature freeze, so forgive me for this (ancien) question : would
it possible to add CREATE OR REPLACE VIEW and CREATE OR REPLACE TRIGGER in
current PostgreSQL 7.2 release?

No. RC1 is *tomorrow*, and we're not pushing it back to add features.

Otherwise, it will take another year before
these long-needed features are added.

I'd like to ask people not to adopt the mindset that PG releases are a
year apart. I know it's been that way for the last two, but the project
goals are still to have a release every four-to-six months. If we go
into the development cycle with the notion that the next release is a
year out, it will be a self-fulfilling prophecy.

regards, tom lane

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