jhyde at pentaho.com
Fri Feb 5 14:13:48 EST 2010
I presume because Cache is introduced as a physical optimization and the
query has the same semantics if it is not present.
The planner introduces Cache in certain circumstances such as directly under
a Rank function. Maybe the planner is not smart enough to not introduce it
Because of these issues, I'd rather that these kind of optimizations didn't
modify the MDX parse tree at all. In other words, Cache shouldn't be a
function, it should be a Calc. But it is what it is.
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Matt Campbell
Sent: Thursday, February 04, 2010 12:25 PM
To: Mondrian developer mailing list
Subject: [Mondrian] CacheFunDef.unparse()
CacheFunDef has an override for unparse which has the effect of suppressing
the function from the unparsed output. Does anyone know the rationale for
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian