One of optimizer overrides, that a user can specify, is joinStrategy. The functional spec for joinStrategy says following "The joinStrategy property can be used only within a TableExpression, but it must be used in conjunction with the joinOrder property. Do not let the optimizer choose the join order. "
I think this should be stated as a piece of advice, not as an absolute rule. Generally, specifying a join strategy doesn't make much sense unless you already know the join order. That is, the same join strategy wouldn't necessarily be optimal for different join orders. But specifying the join strategy without specifying the join order won't prevent the query from running (except perhaps in some corner cases), nor will it cause the query to return the wrong results.
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo.com/
