2 questions/fixes...<br><br>1. is there a reason for using a toUpper() on the column names in aggregates - AggGen.java. At least in postgres, it makes the sql invalid...(I've removed them at the moment and all seems fine - see below.. no errors raised in testsuite)
<br><br>2. regarding previous problem. As I see it, each AggGen is created on the fly, so if we let the AggGen know what cube it is dealing with, we can ignore measures in the Table from other cubes.<br><br>i.e.<br>FastBatchingCellReader.java
<br>614: final AggGen aggGen = new AggGen(cube.getName(),cube.getStar(), columns);<br><br>and AggGen.java:55<br>// name of cube concerned - ignore measures from other cubes<br> private String cubeName;<br> <br> public AggGen(String cubeName, RolapStar star,
RolapStar.Column[] columns) {<br> this.cubeName=cubeName;<br> ...<br><br>in init():301<br> if (rMeasure.getCubeName()!=cubeName)<br> continue;<br> <br>this seems to fix the AggGen problem.. at least this one.. and running the test suite with these changes produces NO errors.. (except for 1 postgres/grouping sets related.. which was there before)
<br><br>also... if the Promotion sales measure is included (uses measure expression), AggGen fails since it cannot find the column specified by the expression... any ideas?<br>maybe a baseColumn property for Measure expression or something? (just throwing ideas here).
<br><br><br>Haven't got around to the test creation yet... a bit confused..<br><br>Cheers<br>Ati<br><br>