Jon Nelson wrote on 04.04.2012 19:47:
What about a set-returning function that builds the query dynamically and
wrapping that into a view?
That way the view would never change and client would still have the
perspective of a view/table
Your function could pick up the changes automatically e.g. by looking at
information_schema.tables
That sounds pretty cool, but that is beyond my understanding.
I can write a set-returning function easily enough (call it
build_the_huge_table for "clarity"), but the "wrap that into a view"
part throws me.
Could you give me an example?
create view the_huge_table
as
select *
from build_the_huge_table()
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
