[Mondrian] A couple of "best practices" questions

Eric McDermid mcdermid at stonecreek.com
Fri Jun 19 18:01:42 EDT 2009


On Jun 19, 2009, at 3:28 PM, Julian Hyde wrote:
>
> Your 'forceIndex' attribute is too narrowly focused on one area of  
> hints in
> queries. I know people will want to use other kinds of hints. I  
> suggest a
> <Hint> sub-element, with 'type' attribute and text content. It's up  
> to the
> dialect to know how to interpret that type of hint.
>
> Therefore:
>
>    <Dimension foreignKey="my_dim_id" name="foo">
> 	<Hierarchy hasAll="true" allMemberName="All foo"
> primaryKey="my_dim_id" >
>                 <Table name="my_dim" alias="my_dim">
>                     <Hint type="force_index">my_index</Hint>
>                 </Table>
> 		...
> 	</Hierarchy>
>    </Dimension>

Makes sense.  Will do.

>> I can't explain why the original authors did it this way, but as for
>> why I didn't think of it?  It was probably just too flippin'
>> obvious. :)
>
> It's obvious to anyone who has read the SQL standard. All 10 of  
> them. 6 of
> these are dead, and most of the others are wishing they hadn't.

I feel their pain.  I've read several hundred pages of it, and  
percentage-wise that isn't even in double digits.

  -- Eric




More information about the Mondrian mailing list