Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Stop Criteria for Sql Execution

RE: Stop Criteria for Sql Execution

From: Mercadante, Thomas F <thomas.mercadante_at_labor.state.ny.us>
Date: Mon, 7 Mar 2005 13:40:08 -0500
Message-ID: <C9995D8C5E0DDA4A8FF9D68EE666CE0704AC0302@exchsen0a1ma>


Waleed,

Maybe Oracle should be smarter and recognize the craziness of the query.

But then, maybe the developer should also recognize the problem.

Perhaps your frustration is pointing in the wrong direction?

Tom

-----Original Message-----

From: Khedr, Waleed [mailto:Waleed.Khedr_at_FMR.COM] Sent: Monday, March 07, 2005 11:38 AM
To: oracle-l_at_freelists.org
Subject: Stop Criteria for Sql Execution

Why does Oracle have to execute the sql and scan data in a table for a sql like this:

Select * from table
Where column1 is null and column1=3D10

Or=20

Select * from table
Where column1=3D10 and column1=3D20

All the research money going to optimize the optimizer, and still can't take care of simple stuff like this.

Am I missing something?

I will probably start searching for smarter databases :)

Waleed
--

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

http://www.freelists.org/webpage/oracle-l Received on Mon Mar 07 2005 - 13:43:31 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US