From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "W(dot) Matthew Wilson" <matt(at)tplus1(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to intelligently work with views that depend on other views |
Date: | 2015-08-06 22:49:28 |
Message-ID: | 55C3E478.8000506@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/06/2015 01:44 PM, W. Matthew Wilson wrote:
> I have a bunch of views, and some views use data from other views.
>
> For example, view A might get used by view B and view B gets used by view C.
>
> Several times now, as I got further into the project, I've changed how
> I make some views and I've had to redefine not just that view, but all
> the ones that depend on it.
>
> This is getting frustrating! When I want to change how I make view A,
> I have to drop view A cascade, and then view B and view C are dropped.
>
> Then I have to remember to re-create B and C after I rewrite A.
>
> There's likely a better solution...
>
> What is it?
Use some sort of schema versioning and management tool. I have been
using Sqitch(http://sqitch.org/) and have found it very useful for this
sort of thing. There is some setup overhead, but after that going
forward and backwards in your schema management becomes fairly easy. As
a bonus you get a nice record of what you have done and if you write
good comments, why you did it:)
>
> GO POSTGRESQL!
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2015-08-06 22:50:41 | Re: How to intelligently work with views that depend on other views |
Previous Message | W. Matthew Wilson | 2015-08-06 20:44:47 | How to intelligently work with views that depend on other views |