Re: DROP VIEW code question - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: DROP VIEW code question
Date
Msg-id Pine.LNX.4.21.0010172229430.9649-100000@peter.localdomain
Whole thread Raw
In response to DROP VIEW code question  (Mark Hollomon <mhh@mindspring.com>)
Responses Re: DROP VIEW code question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Mark Hollomon writes:

> Also
> 
> "DROP TABLE x, y, z" is allowed, but
> 
> "DROP VIEW x, y, z" is not.
> 
> Any reason other than historical?

I don't know how it looks now, but the "DROP TABLE x, y, z" was pretty
broken a while ago.  For example, if there was some sort of dependency
between the tables (foreign keys?) it would abort and leave an
inconsistent state.  I'm not very fond of this extension, but keep the
issue in mind.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Mark Hollomon
Date:
Subject: DROP VIEW code question
Next
From: Tom Lane
Date:
Subject: Re: DROP VIEW code question