RE: Stop Criteria for Sql Execution
- From: "Mercadante, Thomas F" <thomas.mercadante@xxxxxxxxxxxxxxxxx>
- To: "'Waleed.Khedr@xxxxxxx'" <Waleed.Khedr@xxxxxxx>, oracle-l@xxxxxxxxxxxxx
- Date: Mon, 7 Mar 2005 13:40:08 -0500
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@xxxxxxx]
Sent: Monday, March 07, 2005 11:38 AM
To: oracle-l@xxxxxxxxxxxxx
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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
