Re: Weird behavior of the table with unique index

As others have noted, the problem could well be one of implicit type conversions.

One of the notes I loaded up on to my web site this week describes the problem and runs through a test case which matches your problem very closely.

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Alla Gribov wrote in message <36BE1882.E52FBE9_at_uptick.com>...
>
>I am running "Explain plan" on a following statement
>SELECT * FROM TABLE
>WHERE COLUMN2 = lv_column2
> AND COLUMN1 = lv_column1
>
>Explain plan shows me "Full table scan" instead of "Unique index scan".
>
>Even if I put a hint on this unique index, I am getting "Full index
>scan"
>
Received on Wed Feb 10 1999 - 00:00:00 CET