Table modifications with dependent views - best practices? - Mailing list pgsql-general

From John Browne
Subject Table modifications with dependent views - best practices?
Date
Msg-id ccc606105042119246d6602e6@mail.gmail.com
Whole thread Raw
Responses Re: Table modifications with dependent views - best practices?
List pgsql-general
Ok, I've been using postgres for a-while now, and am curious how you
guys handle this.  What is the best way to make modifications to
tables that have lots of dependent objects, like views?  Do you just
do the obvious drop...cascade and manually re-create your views? Do
you keep your "create view" statements in a text file for this purpose
or just pull them from a pg_dump file?  Is there a better way to
handle this sort of thing?

I know on a properly designed database, changes to the schema are
usually not necessary.  However, during development, database tweaks
(at least for me) are pretty common.

Any thoughts?

pgsql-general by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Record as a parameter to a function
Next
From: Carlos Correia
Date:
Subject: Re: Record as a parameter to a function