On Tue, Jun 30, 2009 at 4:41 PM, Steve Holub<st...@sqlpower.ca> wrote:
> Hey guys,
> Sam would really like us to use the power architect for designing cubes, but
> it still needs a little work. Here are a few comments based on the mondrian
> schema:
> http://mondrian.pentaho.org/documentation/schema.php#Schema_files
> - When you create a new cube, it should only give you the option build it on
> an existing table (or on an aggregate table).
Actually, the Cube can be defined on a table, join or "view"
(arbitrary select statement). From section 3.1 of the file you
referenced:
The fact table is defined using the <Table> element. If the fact table
is not in the default schema, you can provide an explicit schema using
the "schema" attribute, for example
<Table schema=" dmart" name="sales_fact_1997"/>
You can also use the <View> and <Join> constructs to build more
complicated SQL statements.
> - When defining a dimension hierarchy's relation, it should then give you
> the table / view / join / inline table options.
Yes, we will do this. Do you need it ASAP?
> - Time dimension hierarchies should give me the option of defining the
> levelType.
I will try to make sure this is done soon!
> - Presently, I don't think you can add a degenerate dimension (a dimension
> without a dimension table - where the columns are found in the fact table).
> This would be particularly useful when working with summary tables.
I *think* you can do this. Perhaps it's not obvious how to achieve it,
which I'd consider to be a bug. Let me double-check and get back to
you.
> These are the main issues, as far as I can tell. I would say the top two
> being the time levelType and the dimension hierarchy relation definitions.
> Thanks guys,
> Steve
Thanks, Steve! We'll follow up on this.
-Jonathan