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

> 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.