Re: Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ?

From: Nilo Segura <nilosegura@xxxxxxxxx>
To: Oracle List <oracle-l@xxxxxxxxxxxxx>
Date: Tue, 8 Feb 2011 18:35:12 +0100

Ok, after some kind replies, I understood why it has to run the
partition range all. I did the mistake of generalizing a particular
case I was handling.

thanks!
--
//www.freelists.org/webpage/oracle-l

References:
- Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ?
  - From: Nilo Segura

Other related posts:

» Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ?- Nilo Segura
» Re: Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ?- Maxim Demenko
» Re: Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ? - Nilo Segura