How to intelligently work with views that depend on other views

From: "W(dot) Matthew Wilson" <matt(at)tplus1(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: How to intelligently work with views that depend on other views
Date: 2015-08-06 20:44:47
Message-ID: CAGHfCUCwbY3RtOWxWa7mJJ7ubTio_iqY3bEATDrGXOSr4HHppg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

GO POSTGRESQL!

--
W. Matthew Wilson
matt(at)tplus1(dot)com
http://tplus1.com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-08-06 22:49:28 Re: How to intelligently work with views that depend on other views
Previous Message Jim Nasby 2015-08-06 19:36:44 Re: multiple postgres processes after establishing tcp connection