AnySQL (d.c.b.a) wrote: > The "INDEX" hint let Oracle automatically choose index, however if > Oracle can introduce a new hint "INDEX_COL", it will really helpful.
> Because we may use different index name for the same table in different > environment (PROD vs QA).
> And to use column on specific column is easy for developer to > understand.
Naming the indexes the same across environments would be a lot easier than getting Oracle to change their RDBMS code. Perhaps you should just synchronize your environments. That's what I would do. -- To reply by email remove "_nospam"
AnySQL (d.c.b.a) wrote: > The "INDEX" hint let Oracle automatically choose index, however if > Oracle can introduce a new hint "INDEX_COL", it will really helpful.
> Because we may use different index name for the same table in different > environment (PROD vs QA).
> And to use column on specific column is easy for developer to > understand.
Why do you even want to use different index names? What pressing business need is resolved using this requirement? Do you really think it makes sense to use different names?
AnySQL (d.c.b.a) wrote: > The "INDEX" hint let Oracle automatically choose index, however if > Oracle can introduce a new hint "INDEX_COL", it will really helpful.
> Because we may use different index name for the same table in different > environment (PROD vs QA).
> And to use column on specific column is easy for developer to > understand.
Why should Oracle add a hint to cover for the horrifyingly bad discipline and practices of a development team?
If the indexes have different names the DBA should be asked to resign. -- Daniel A. Morgan http://www.psoug.org damor...@x.washington.edu (replace x with u to respond)
AnySQL wrote: >The "INDEX" hint let Oracle automatically choose index, however if >Oracle can introduce a new hint "INDEX_COL", it will really helpful.
You got it backwards. Hinting HINDERS the ability to let Oracle automatically choose the index. If your developers are having to put in a lot of hints, there is perhaps something wrong with their perception of CBO.
Is it really so hard for your developers to understand they should be explicitly naming everything consistently?
Sybrand Bakker wrote: > On Mon, 06 Mar 2006 10:58:49 -0800, DA Morgan <damor...@psoug.org> > wrote:
>>If the indexes have different names the DBA should be asked to >>resign.
> Aren't the customary exit procedures in the US (unlike many civilized > coutnies) quite different?
> -- > Sybrand Bakker, Senior Oracle DBA
Absolutely ... an unfortunatly. Honor and personal integrity are quaint attributes of earlier generations. -- Daniel A. Morgan http://www.psoug.org damor...@x.washington.edu (replace x with u to respond)
AnySQL (d.c.b.a) wrote: > The "INDEX" hint let Oracle automatically choose index, however if > Oracle can introduce a new hint "INDEX_COL", it will really helpful.
> Because we may use different index name for the same table in different > environment (PROD vs QA).
> And to use column on specific column is easy for developer to > understand.
In 10g, there is an improved version of INDEX hint
INDEX(tab1 tab1(ind_col1, ind_col2))
By specifying the index columns rather than the index name, Oracle can pick up any index with these columns as the leading portion of the index key. When you think about it it's a much better hint, approaching the problem from the right direction - the search criteria from the logical perspective rather than a particular physical object.
oracle_doc wrote: > AnySQL (d.c.b.a) wrote: > > The "INDEX" hint let Oracle automatically choose index, however if > > Oracle can introduce a new hint "INDEX_COL", it will really helpful.
> > Because we may use different index name for the same table in different > > environment (PROD vs QA).
> > And to use column on specific column is easy for developer to > > understand.
> In 10g, there is an improved version of INDEX hint
> INDEX(tab1 tab1(ind_col1, ind_col2))
> By specifying the index columns rather than the index name, Oracle can > pick up any index with these columns as the leading portion of the > index key. When you think about it it's a much better hint, approaching > the problem from the right direction - the search criteria from the > logical perspective rather than a particular physical object.
Hi, oracle_doc,
You're one of the few gentlemen that have good memory! About this day last year, Jonathan Lewis told us this (still) undocumented feature