Re: Add OR REPLACE clauses to non-FUNCTION object creation in PostgreSQL 7.3

From: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
To: "Kaare Rasmussen" <kar(at)kakidata(dot)dk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add OR REPLACE clauses to non-FUNCTION object creation in PostgreSQL 7.3
Date: 2002-01-24 15:59:22
Message-ID: 200201241559.g0OFxML26596@www1.translationforge
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Isn't it the same as
>
> DROP VIEW name
> CREATE VIEW name
> or
> DROP TRIGGER name
> CREATE TRIGGER name

Two examples :
1) Views with triggers
If you drop a view which has triggers and then re-recreate the view, the
triggers are lost.

2) Server side code consistency
Let's say you are working on a large view in pgAdmin II. If you drop a view
and recreate it, you can never be sure that the new version of the view will
ba accepted by PostgeSQL.

i.e. if the view definition is not correct, you loose your work.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2002-01-24 16:12:54 Re: PostgreSQL crashes with Qmail-SQL
Previous Message Justin Clift 2002-01-24 15:50:05 Re: 7.1.4