-
Amen to that. If someone ever needs olap4j on JDK 1.4, let us know. We'll cross the bridge when we get there.
2009-10-02 16:56:54 UTC in olap4j
-
Hi Thomas. When we created the query model, we had to deal with an underlying disparity between what cube contains and what is actually selected to be part of the query. When you build a query, that means that a member can part of many selections at the same time. Therefore, there are no straight ways to remove a given member from a query without prior knowledge of which selection contains it.
2009-10-02 16:45:35 UTC in olap4j
-
lucboudreau committed revision 284 to the olap4j SVN repository, changing 1 files.
2009-10-02 13:59:50 UTC in olap4j
-
lucboudreau committed revision 283 to the olap4j SVN repository, changing 1 files.
2009-10-02 13:39:07 UTC in olap4j
-
Fixed in revision 281.
2009-09-30 20:21:33 UTC in olap4j
-
lucboudreau committed revision 281 to the olap4j SVN repository, changing 1 files.
2009-09-30 20:20:56 UTC in olap4j
-
This was fixed a while ago,
2009-09-30 19:56:35 UTC in olap4j
-
When no dimensions are included on a query axis, there was an index out of bounds exception thrown. Now it simply skips the axis.
Fixed in revision 280.
One can still validate his query object with the Query.validate() method prior to execution to detect any potential problems. The exception then returned is this :
Exception in thread "main" org.olap4j.OlapException...
2009-09-30 19:33:26 UTC in olap4j
-
lucboudreau committed revision 280 to the olap4j SVN repository, changing 1 files.
2009-09-30 19:31:10 UTC in olap4j
-
I can fix that. Hold on.
2009-09-30 19:09:39 UTC in olap4j
Luc Boudreau
