Open ghost opened 10 years ago
I've managed to use materialized views in PostgreSQL with Pentaho/Mondrian just by simply editing the schema file by hand, but it seems to me that the problem runs deeper and also disallows the usage of aggregate tables for a fact table that's actually a materialized view. It looks like AggTableManager skips my fact table while searching for aggregate tables.
Was just hit by this one. As seen above, it's a simple fix.
Had to revert to standard views for now (don't have so much data t hat I absolutely needed mat views). Hope this will be fixed soon.
This is a pull request I made adding support for Materialized Views https://github.com/pentaho/mondrian/pull/731
Mondrian reports "table not found" error, when a PostgreSQL MATERIALIZED VIEW is defined as
<Table>
within<PhysicalSchema>
. Storing the data as regular table is a workaround.I recently posted an issue at the pgjdbc project, assuming that this component causes the error. But in fact, mondrian seems to cause the problem, neither asking PostgreSQL for mat. views nor foreign tables.
Please visit:
https://github.com/pgjdbc/pgjdbc/issues/166
https://github.com/jOOQ/jOOQ/issues/3254
Thank you!