On 25 Apr 2010, at 07:34, Scott Bailey wrote:
>
>> I can point you to the relevant code in GitHub if you're interested (it's
>> Java).
>
> Absolutely. Thanks
>
> Scott Bailey
Line 813 of
http://github.com/okohll/agileBase/blob/master/gtpb_server/src/com/gtwm/pb/model/manageSchema/DatabaseDefn
Scott,
I implemented a system exactly like this for the app in my signature below.
Basically the system stores metadata containing each view definition and the
joins between them. When someone needs to alter a view, say to remove a column,
a DROP CASCADE is performed then each view is recreated
Using views in Postgres can be a painful process. Changing a column in a
base table will require you to drop all views that depend on it, and all
views that depend on those views and so on.
My coworker was complaining this morning that he now has a bunch of
queries where a view is joined back
