-
What answer were you hoping to get? Given the set {10, 20, 30, 40, 50}, what is the 95th percentile?.
2009-11-20 07:29:21 UTC in JPivot - a JSP based OLAP client
-
The order of XML elements within the Mondrian schema file is very sensitive. NamedSet elements must come after all Measure and CalculatedMember elements in the cube. Elements that come in the wrong order are silently ignored.
2009-11-10 17:27:27 UTC in JPivot - a JSP based OLAP client
-
jhyde committed revision 291 to the olap4j SVN repository, changing 1 files.
2009-10-20 17:56:29 UTC in olap4j
-
jhyde committed revision 290 to the olap4j SVN repository, changing 2 files.
2009-10-18 23:50:49 UTC in olap4j
-
jhyde committed revision 289 to the olap4j SVN repository, changing 1 files.
2009-10-18 06:35:47 UTC in olap4j
-
jhyde committed revision 288 to the olap4j SVN repository, changing 3 files.
2009-10-17 19:53:39 UTC in olap4j
-
Paul I just saw your comment dated 2009-10-16 13:42. I haven't tested against SSAS. If SSAS behaves differently -- e.g. if it to be always set inside -- then please reopen.
The behavior of the getCubes method has to be the same across all drivers and across all XMLA servers. If you pass in catalog=null to that method, we have no choice but to iterate over all...
2009-10-17 19:40:02 UTC in olap4j
-
Fixed in svn revision 287.
2009-10-17 09:06:36 UTC in olap4j
-
jhyde committed revision 287 to the olap4j SVN repository, changing 12 files.
2009-10-17 09:06:18 UTC in olap4j
-
XmlaOlap4jConnection.java line 808, which Paul correctly says is at the heart of the problem, was added by Luc in revision 115 in response to this thread: https://sourceforge.net/forum/forum.php?thread_id=2248227&forum_id=577988
The JDBC doc for DatabaseMetaData.getSchemas is clear. It needs to return all schemas in all catalogs. Therefore we should not use Connection.getCatalog to restrict...
2009-10-16 21:40:33 UTC in olap4j
