The hinted is documented in 9.2, so I would
take the viewpoint that perhaps the hint is
supposed to be used, but has only been
undocumented because of the time-lag
between production code and documentation.
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
____Belgium__November (EOUG event - "Troubleshooting")
____UK_______December (UKOUG conference - "CBO")
Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
"Richard Kuhler" <noone_at_nowhere.com> wrote in message
news:ReWkb.57734$th6.21460_at_twister.socal.rr.com...
> When using a pipeline table function in a query, it appears that
Oracle
> uses the default statistics for that source (nothing surprising
about
> that). Unfortunately, this often leads it to make some bad
decisions
> about the execution plan. I could of course use the well documented
> hints to explicitly tell the optimizer which join methods to use,
table
> order, etc... However, I'd rather not interfere with the optimizer
any
> more than I have to. Along that line, I've tested things using the
> undocumented CARDINALITY hint and that gets things back on track
nicely.
> Obviously, using an undocumented feature has it's own risks.
>
> What's your opinion?
> Any other suggestions?
>
> --
> Richard Kuhler
>
Received on Tue Oct 21 2003 - 09:11:26 CDT
