[Mondrian] Util.lookupCompound MatchType BEFORE
remberson at edgedynamics.com
Mon Mar 5 13:20:50 EST 2007
Should I merge my NullValueUdf test (in mondrian.udf) into
the UdfTest.java file in mondrian.test?
Julian Hyde wrote:
> Sounds like this problem could be expressed as an MDX testcase. Whoever
> fixes this, please add an MDX test to UdfTest.
> ("You know my methods, Watson.")
>> -----Original Message-----
>> From: mondrian-bounces at pentaho.org
>> [mailto:mondrian-bounces at pentaho.org] On Behalf Of Zelaine Fong
>> Sent: Monday, March 05, 2007 9:04 AM
>> To: Mondrian developer mailing list
>> Subject: Re: [Mondrian] Util.lookupCompound MatchType BEFORE
>> I believe I put in that code. And you're right. It should
>> be returning
>> the last child of bestChild's previous sibling. Is this
>> something you
>> need a fix for a right away?
>> -- Zelaine
>> Richard Emberson wrote:
>>> This is a question concerning what happens when the
>>> match type is MatchType.BEFORE.
>>> In the method Util.lookupCompound(), there is a comment:
>>> // if we're doing a non-exact match, and we find a non-exact
>>> // match, then for an after match, return the first child
>>> // of each subsequent level; for a before match, return the
>>> // last child
>>> I understand why the match type AFTER returns the next child,
>>> , but why for match type BEFORE is the last child in the same
>>> list returned,
>>> childrenList.get(children.length - 1);
>>> Why is it not the last child in the bestChild's previous
>>> sibling returned?
>> Mondrian mailing list
>> Mondrian at pentaho.org
> Mondrian mailing list
> Mondrian at pentaho.org
Quis custodiet ipsos custodes:
This email message is for the sole use of the intended recipient(s) and
may contain confidential information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.
More information about the Mondrian