Re: materialized views and ORDER BY
- From: "Gints Plivna" <gints.plivna@xxxxxxxxx>
- To: spikey.mcmarbles@xxxxxxxxx
- Date: Wed, 25 Apr 2007 20:23:33 +0300
2007/4/25, Greg Norris <spikey.mcmarbles@xxxxxxxxx>:
I have a developer who's complaining that the ORDER BY clause is being
dropped from his materialized views, thus requiring him to recreate them
several times a day. I've told him I'm virtually certain this is by design,
so that the MV behavior doesn't change depending upon the refresh method,
but have so far been unable to find it explicitly documented... can anyone
point me to a definitive statement?
MV data are stored just like table data. Oracle never ever guaranteed
that someone will get back rows in any particular order from tables.
That's also true for MVs. So if you need to get data from MVs ordered
the only guaranteed approach is to add order by clause.
Gints Plivna
http://www.gplivna.eu
--
http://www.freelists.org/webpage/oracle-l
- Follow-Ups:
- Re: materialized views and ORDER BY
- From: Greg Norris
- References:
- materialized views and ORDER BY
- From: Greg Norris
Other related posts:
- » materialized views and ORDER BY
- » Re: materialized views and ORDER BY
- » RE: materialized views and ORDER BY
- » Re: materialized views and ORDER BY
- » Re: materialized views and ORDER BY
- » Re: materialized views and ORDER BY
I have a developer who's complaining that the ORDER BY clause is being dropped from his materialized views, thus requiring him to recreate them several times a day. I've told him I'm virtually certain this is by design, so that the MV behavior doesn't change depending upon the refresh method, but have so far been unable to find it explicitly documented... can anyone point me to a definitive statement?
- Re: materialized views and ORDER BY
- From: Greg Norris
- materialized views and ORDER BY
- From: Greg Norris