[Mondrian] Multiple sets in where clause

Pedro Alves pmgalves at gmail.com
Fri May 4 05:06:31 EDT 2012


Crossjoin works just as I want. Initially I'd think it would be 
inefficient but works great for what I'm working on. Will keep you 
posted

On Fri 04 May 2012 05:37:47 AM WEST, Julian Hyde wrote:
>>> On Thu 03 May 2012 05:27:34 PM WEST, Pedro Alves wrote:
>>>> Is it supported without ussing calculated (aggregated) members?
>>>>
>>>> Where <set> works.
>>>>
>>>> where (<member>,<member>) works
>>>>
>>>> where ( <set> * <set> works but this isn't a very optimal approach.
>>>>
>>>> I feel I'm missing something very very obvious
>
> Pedro you may be missing something obvious but I'm not sure what it is.
>
> Remember that in MDX:
>
>   *  ( ... ) is the syntax for a tuple. Members must be from different
>     hierarchies.
>   * { ... } is the syntax for a set. Elements in the set must be
>     members (or tuples) with the same dimensionality.
>
>
> You can write
>
> WHERE {h1.m1, h1.m2} * {h2.m1}
>
> or
>
> WHERE CROSSJOIN({h1.m1, h1.m2},  {h2.m1})
>
> or
>
> WHERE {(h1.m1, h2.,1), (h1.m2, m2.m2)}
>
> and they are all valid and equivalent.
>
>
>> Am 03.05.2012 um 18:30 schrieb Pedro Alves <pmgalves at gmail.com
>> <mailto:pmgalves at gmail.com>>:
>>
>>> Bah - from http://jira.pentaho.com/browse/MONDRIAN-555 I take it it's a
>>> no? :S
>
> No, that bug only relates if you have ancestor and descendant members
> in the same set. It will affect totals to a value that is arguably
> wrong, but the slicer should still work.
>
> Julian
>
>
>
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian


More information about the Mondrian mailing list