Re: rm RULE based optimizer != GOOD IDEA

Khe, khe You didn't do the quoting precisely, I didn't say "can't wait until <hint name here> hint is removed", though I did say "I'm planning to allow [for our developed applications] if blabla...". That's a bit different.

Of course it is the problem of review process. But we are not alone here I think.

But the main problem what I wanted to explain with that was: that our developer didn't know HOW RBO worked, he simply tried several hints and that one appeared to work. And while for example Hash join or Index hint is more or less easier to understand, RBO is more complicated and hides more sunken rocks. Just my thoughts here...

Gints

On 4/25/05, Post, Ethan <Ethan.Post_at_ps.net> wrote:
> or..."one of our developers used HASH JOIN hints all throughout their
> SQL, now we had to go back and remove them and this took time and $$$,
> can't wait until HASH JOIN hint is removed."
>=20
> you see the problem in this case and the case below has to do with the
> review process, not the mere existence of the hint
>

--
http://www.freelists.org/webpage/oracle-l