db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Optimizer overrides - functional spec
Date Thu, 15 Sep 2005 07:47:56 GMT
Yes, you are right. Since -- comments gobble everything until the end of 
line by their definition, I didn't put anything in the functional spec for 
it. But it never hurts to be more specific to make things clearer. I would 
go ahead and put this information in the functional spec.
 thanks,
Mamta
 On 9/15/05, Jeffrey Lichtman <swazoo@rcn.com> wrote: 
> 
> 
> >I am looking at implementing optimizer overrides in Derby for 10.2
> >release. Derby engine in fact already supports some optimizer
> >overrides but they are not user visible. I have attached the
> >functional spec for more information. Let me know if anyone has any 
> comments.
> 
> I assume that since the override syntax will be in comments, any
> override must be at the end of a line. For example:
> 
> FROM --PROPERTIES joinOrder = FIXED
> tab1, tab2, tab3
> 
> would work, but:
> 
> FROM --PROPERTIES joinOrder = FIXED tab1, tab2, tab3
> 
> would not work. Is that correct? If so, I think it should be
> explained in the functional spec.
> 
> 
> - Jeff Lichtman
> swazoo@rcn.com
> Check out Swazoo Koolak's Web Jukebox at
> http://swazoo.com/
> 
>

Mime
View raw message