RE: Re[2]: Hotsos Symposium, Day 1

  • From: "Andre van Winssen" <awinssen@xxxxxxxxx>
  • To: <jknight@xxxxxxxxxxxxxx>, <davewendelken@xxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 9 Mar 2005 19:16:15 +0100

This must be RBO times, because 1=1 evaluates to TRUE and will be neglected
by CBO since it does not add anything new to CBO considerations (event

I hope I am not wrong, otherwise I loose faith in cbo intelligence.
That is bad because cbo is today's Oracle RDBMS engine.

Andre van Winssen

-----Oorspronkelijk bericht-----
Van: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
Namens Knight, Jon
Verzonden: woensdag 9 maart 2005 17:25
Aan: 'davewendelken@xxxxxxxxxxxxx'; oracle-l@xxxxxxxxxxxxx
Onderwerp: RE: Re[2]: Hotsos Symposium, Day 1

  This is exactly the reason I adopted the practice some time ago.  I used
to take them out when pasting the query into a package, etc.  But, not so
much anymore.  With sufficient proof of performance degredation, I would
take them out at once.

Jon Knight

 -----Original Message-----
From:   oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of David Wendelken
Sent:   Wednesday, March 09, 2005 10:07 AM
To:     oracle-l@xxxxxxxxxxxxx
Subject:        RE: Re[2]: Hotsos Symposium, Day 1

>I guess what I'm looking for is --- is there a good, positive 
>reason to use an expression like 1=1?

I have a colleague who uses WHERE 1 = 1 all the time.
I asked him why some years ago.
It was because as he tuned or modified statements, 
he got tired of re-arranging the WHERE and AND clauses all the time.
By starting off with WHERE 1 = 1, all the clauses that he would be
re-arranging started with AND, so it saves him some bother.

Best reason I've heard so far.



Other related posts: