You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2019. It is now read-only.
Found a very subtle problem with Mondrian's DelegatingRole, that when it wraps RolapMember instance into RolapHierarchy$LimitedRollupMember, they no longer return true when equals() method is invoked with the other as an argument, which could make various parts of Pivot4J not functioning properly.
So, it would be safe to compare between unique name properties of members instead of the member objects themselves to prevent such a problem.
The text was updated successfully, but these errors were encountered:
I'll change the relevant code to be as defensive as possible. Though it's not viable to change all the cases like checking for .contains() on List of members without making codebase a mess, so the full resolution would be possible when below issue is addressed from Mondrian project:
Found a very subtle problem with Mondrian's DelegatingRole, that when it wraps RolapMember instance into RolapHierarchy$LimitedRollupMember, they no longer return true when equals() method is invoked with the other as an argument, which could make various parts of Pivot4J not functioning properly.
So, it would be safe to compare between unique name properties of members instead of the member objects themselves to prevent such a problem.
The text was updated successfully, but these errors were encountered: