From: | Andreas <maps(dot)on(at)gmx(dot)net> |
---|---|
To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Flexibility of views and functions? |
Date: | 2009-07-14 00:54:44 |
Message-ID: | 4A5BD754.4070007@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I need to do some reporting for projects that have some columns that
stay the same for every project and then every project brings along some
project specific stuff.
Now I've got a big view for everyone of those about 100 projects (and
growing) that is about 80% the same as every other view.
I'd like to strip the constant part into a central view holding those
common columns like "tvw_big_thing"
then have for every project some
SELECT tvw_big_thing.*, c1, c2, ..., cn ...
where c1...cn would be project specific.
I'dread the day when mr. boss comes along to tell me he likes
tvw_big_thing altered.
All dependend views would have to be dropped and recreated, am I right?
I figured a function as cool, too like
fct_big_thing(project_id::integer)
it could do the filtering :)
I'd be cool to have depending views show the "inherited" columns that
get delivered on call time.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-07-14 02:37:02 | Re: [GENERAL] pg_migrator not setting values of sequences? |
Previous Message | Bruce Momjian | 2009-07-14 00:36:22 | Re: [GENERAL] large object does not exist after pg_migrator |