Table modifications with dependent views - best practices?

From: John Browne <jkbrowne(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Table modifications with dependent views - best practices?
Date: 2005-04-22 02:24:49
Message-ID: ccc606105042119246d6602e6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Carlos Correia 2005-04-22 02:31:59 Re: Record as a parameter to a function
Previous Message Michael Fuhr 2005-04-22 02:18:11 Re: Record as a parameter to a function