Re: Re: Re: Index not used to avoid sort with calculated column

From: <l.flatz_at_bluewin.ch>
Date: Thu, 27 Jun 2019 11:13:24 +0200 (CEST)
Message-ID: <714349598.13843.1561626804692_at_bluewin.ch>


Hi Jonathan

OMG. Yes, of course. Head banging ...

Thanks

Lothar
----Ursprüngliche Nachricht----
Von : jonathan_at_jlcomp.demon.co.uk
Datum : 27/06/2019 - 10:40 (MS)
An : oracle-l_at_freelists.org
Betreff : Re: Re: Index not used to avoid sort with calculated column

With the usual warning that including "invisible" is highly desirable in 12c to pre-empt the threats of: select * ....
and
insert without (list of columns)

Regards
Jonathan Lewis



From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of l.flatz_at_bluewin.ch <l.flatz_at_bluewin.ch> Sent: 27 June 2019 08:57
To: tanel_at_tanelpoder.com
Cc: martin.a.berger_at_gmail.com; oracle-l_at_freelists.org Subject: Re: Re: Index not used to avoid sort with calculated column

Hi Tanel,

thanks for your help. I is good to have collegues who can help. I was suspecting something like that, but I am up to my neck in work and could not affort testing on suspicion. As from the doc I think going for the virtual column being preferrable. It avoids using an underscore parameter.

drop index e_low_sort1;
alter table emp add (low_job as (lower(job)) virtual); create index e_low_sort1 on emp (low_job, hiredate);

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Thu Jun 27 2019 - 11:13:24 CEST

Original text of this message