ordered_hint

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1

If you have a query that joins table t1 and view v1, and the query uses an ORDERED hint, exactly what order will the optimizer join the tables in? Will it use t1 as the driving table and join the tables in v1 in the same order they're listed in the view's FROM clause? Or will the order they're listed in the view be irrelevant? I was looking for documentation on this but didn't find any. The Performance Tuning Guide only deals with the scenario where everything in the FROM clause is a table.

example:

select --+ordered
  t1.cola, v1.colb
from t1, v1
where t1.colx = v1.coly

Oracle version in question is 9.2.0.5.

• -- To reply by email remove "_nospam"
  -----BEGIN PGP SIGNATURE-----
  Version: GnuPG v1.4.0 (MingW32)

iEYEARECAAYFAkMxs+kACgkQzIf+rZpn0oTpMQCghhfqwNRlRuCMsRUlbq3WYj3b g7YAoIAckJ5D9L7CItTXsxq2lRZtFGRC
=Pgin
-----END PGP SIGNATURE-----
Received on Wed Sep 21 2005 - 14:26:33 CDT