MDX -> Query Model

0 views
Skip to first unread message

luizfox

unread,
May 30, 2008, 7:19:42 AM5/30/08
to Halogen Development
About the Halogen's Issue 6...

the best solution to implement this is to use olap4j to get the
metadata, or can I just get the MDX string and transform it to the
query model using the createSelection() method (just a service)?

What do you think?

william...@gmail.com

unread,
Jun 1, 2008, 3:46:04 PM6/1/08
to Halogen Development
My choice would be to parse the MDX string and create the selections
directly with the query model. At this point you'll only be able to
do a subset of the entire MDX since you can't create calculated
members or format strings with createSelection(). Maybe we can get
the Olap4J guys to implement this stuff for us.

If we could get just straight parsing of MDX with dimension and member
selections that would be great.

Bill

luizfox

unread,
Jun 2, 2008, 5:04:58 PM6/2/08
to Halogen Development
Another question is how the selections are parsed to MDX.

What's difference between "Member" and "Children" options on popup? It
seems that the same code is being parsed to the olap engine, but just
replicated when it's Children.

Am I correct?

william...@gmail.com

unread,
Jun 4, 2008, 6:20:38 AM6/4/08
to Halogen Development
I'm not sure how children is implemented in the engine but I do know
that olap4j offers selection modes (including children, member... etc)
that are the same as all the one implemented in the halogen gui. So
you wouldn't have to directly parse the MDX and (in the case of
children) iterate all the children of a given member. olap4j will do
that for you. In other words once you've parsed a member selection
and found that it's children then you just need to select children on
that member in olap4j.

Bill

luizfox

unread,
Jun 4, 2008, 1:48:59 PM6/4/08
to Halogen Development
I'm getting the string, analyzing it (without olap4j), sending to the
client and setting the interface.
I'm not sure where olap4j comes in. So, do you suggest that the
analysis should be done with olap4j?

luizfox

unread,
Jun 4, 2008, 3:44:16 PM6/4/08
to Halogen Development
I just realized that with olap4j, the work is a lot easier...

william...@gmail.com

unread,
Jun 4, 2008, 4:38:44 PM6/4/08
to Halogen Development
I thought it might be since you didn't have to round trip the parsing
and execution of the query.

Sounds like you're making good headway. I think the goal here is to
be able to parse any of the MDX that is created by the execution of
the query model. In other words, model so that it can parse anything
it is able to create that way we elminate calculations and styles.

Bill
Reply all
Reply to author
Forward
0 new messages