Chris,
This is exactly what extensible indexing was created for. The idea is simple:
You implement an effective search (typically involving some helper tables/indexes),
and you express your "search" using a function in SQL, that will call out
to your implementation. The actual implementatio
Title: RE: Oh Where Oh Where Is My Redo Coming From
Chris,
I could be wrong, but I was under impression that parameter to the F in
FBI needed to be either hard coded values or db table columns. I don't think
they could be variables.
But then again I have been wrong ...
Raj
Sent: Friday, July 12, 2002 9:18 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: Function based indexes
I don't think that will work. If you need this to work in a SQL statement in
SQL*Plus, what you can do is something like this:
create or replace package types
as
I don't think that will work. If you need this to work in a SQL statement in
SQL*Plus, what you can do is something like this:
create or replace package types
as
type cursorType is ref cursor;
end;
/
create or replace function sp_ListEmp
( col_value_in my_table.my_column
Harvinder - I had to make these settings in order to use function-based
indexes maybe a year ago in Oracle 8.1.6, and thus far have experienced no
ill effects. For specifics of what they do, I would read the Oracle
documentation and do a search on http://www.google.com. Try it on your test
databas
Sergey,
I did
a quick test which indicates that no special path is mentioned when using a FBI,
instead the execution plan will show that an index is being used, which it would
not do if a FBI had not been set up.
The
example below shows what I mean
HTH
John
SQL> create index joh
