Thomas Pasch <thomas.pasch@xxxxxxxxx> writes: > well, the reason I'm asking is that this *is* posible in Oracle DB. For > me it looks like that the DB knows that the view is broken. You can't > use it, *but* it is still there (and it will be usable again when the > view query is valid again). > I completely agree that the view should be usable again at the end of > transaction (even thus Oracle DB doesn't impose that either), but drop > and re-create the objects in correct order is painful. Well, if the dependent objects don't need to be touched because the view's API (its output column set) isn't changing, then you can use CREATE OR REPLACE VIEW. If the output column set *is* changing, you need to redefine all the dependent objects anyway. Oracle may be willing to guess at what should happen to them, but Postgres isn't. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
