MONDRIAN

Modified DrillThroughQuerySpec to handle cases where DatabaseMetaData returns 0 for getMaxColumnNameLength(). From DatabaseMetaData: "a result of zero means that there is no limit or the limit is not known." The code now interprets zero as no limit. [git-p4: depot-paths = "//open/mondrian/": change = 11319]
pentaho · Jul 18, 2008 · c021ebc · c021ebc
1 parent 94dbc4d
commit c021ebc
Showing 1 changed file with 9 additions and 5 deletions.
diff --git a/src/main/mondrian/rolap/agg/DrillThroughQuerySpec.java b/src/main/mondrian/rolap/agg/DrillThroughQuerySpec.java
@@ -33,14 +33,18 @@ class DrillThroughQuerySpec extends AbstractQuerySpec {
     private final List<String> columnNames;
     private final int maxColumnNameLength;
 
-    public DrillThroughQuerySpec(
-        CellRequest request,
-        boolean countOnly)
-    {
+    public DrillThroughQuerySpec(CellRequest request, boolean countOnly) {
         super(request.getMeasure().getStar(), countOnly);
         this.request = request;
-        this.maxColumnNameLength =
+        int tmpMaxColumnNameLength =
             getStar().getSqlQueryDialect().getMaxColumnNameLength();
+        if (tmpMaxColumnNameLength == 0) {
+            // From java.sql.DatabaseMetaData: "a result of zero means that 
+            // there is no limit or the limit is not known"
+            maxColumnNameLength = Integer.MAX_VALUE;
+        } else {
+            maxColumnNameLength = tmpMaxColumnNameLength;
+        }
         this.columnNames = computeDistinctColumnNames();
     }