And this is what Jonathan Lewis said before, "The thing above might not =
be a valid hint as the <table> might have been given an alias. If the =
table does not have an alias, then this [index hint] will be obeyed, =
unless some conditions relating to null columns could make the indexed =
path return the wrong path [n.b. should that be 'wrong result set'], or =
(prior to skip scans) there was no optimizer mechanism for using the =
index."
> -----Original Message-----
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Bobak, Mark
>=20
> Actually, it will ignore the index if the columns are=20
> nullable, even if =3D
> no null values currently exist. If you repeat your experiment w/ a =
=3D
> primary key or unique index, I think you'll find Oracle will use the =
=3D
> index when directed to do so by a hint, even if it's less=20
> efficient to =3D
> do so.
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Fri Feb 06 2004 - 14:49:39 CST
