Suresh Thalamati wrote:
Mike Matrigali wrote:
Mike Matrigali wrote:
<snip>
Ok, didn't realize this broke the model. As long as the info gets down
to store I don't really care how. So if you can't get the info from
the template we pass down, then we should just add another array
argument to createConglomerate and createAndLoadConglomerate which would
make it look like (this was the approach taken to pass down the
columnOrdering which is basically ascend/descend info for indexes):
long createConglomerate(
String implementation,
DataValueDescriptor[] template,
ColumnOrdering[] columnOrder,
CollationIds[] collationIds,
Properties properties,
int temporaryFlag)
throws StandardException;
I didn't mean to create a new datatype for the collation id's,
I think int or long is fine.
long createConglomerate(
String implementation,
DataValueDescriptor[] template,
ColumnOrdering[] columnOrder,
int[] collationIds,
Properties properties,
int temporaryFlag)
throws StandardException;
Mike ,
Any particular reason why you don't want add collationIds, to the
already existing ColumnOrdering information, instead of
passing it as separate int[] array.
That looks like a good idea. It will take generating a ColumnOrdering
when we create a heap, where we didn't before but that should not be
too hard. We use this for sorting also so it does seem like a natural
place for it.
Thanks
-suresh
