Re: view management

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "Merlin Moncure" <mmoncure(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: view management
Date: 2007-11-16 22:47:01
Message-ID: 200711161547.01425.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday 16 November 2007 2:48 pm, Scott Marlowe wrote:
> On Nov 16, 2007 3:43 PM, Ed L. <pgsql(at)bluepolka(dot)net> wrote:
> > That looks about as ugly as can be. Ugh. What it appears
> > to boil down to is that views become unusable unless you are
> > willing to invest the effort in a complex build system. The
> > DB should handle this issue automatically. Does Oracle?
>
> Really? I find a build system to be a pretty necessary part
> of enterprise development. I can't imagine trying to keep
> track of what I've done to my db without using some kind of
> simple .sql scripts with all my ddl in them.
>
> And I use views and user defined functions a lot.

The overall schema upgrade management system is not the difficult
part. I find the difficulty comes with, for example, 5 levels
of view dependencies. The view you want to update requires you
to rebuild 15 others, which in turn requires you to trace back
another 15 views, and so on until you reach the leafs of the
tree. You don't know those dependencies when you create the
first few views. Maybe you just manually discover all these
dependency paths each time you decide to change a view with
dependencies. That's the part I'm griping about and for which I
was hoping for a better way.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-11-16 23:06:30 Re: public schema doubt
Previous Message Tom Hart 2007-11-16 22:43:44 Re: convert access sql to postgresql