Materilized View [message #296794] |
Tue, 29 January 2008 01:38 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
sachin_svaidya
Messages: 15 Registered: March 2006 Location: Mumbai
|
Junior Member |
![v_sachinmca%40yahoo.com](/forum/theme/orafaq/images/yahoo.png)
|
|
Hi I have one doubt while using M.view, It the Remote data acess is unavailable for some time due to link down, So can I get the contineous access to the M.View object on local database ?
thanks in advance
sv
|
|
|
Re: Materilized View [message #296803 is a reply to message #296794] |
Tue, 29 January 2008 02:00 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](http://www.orafaq.com/forum/images/custom_avatars/72104.gif) |
Littlefoot
Messages: 21818 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
If we consider an "ordinary" view a stored query, it means that - when you select from a view - this "stored query" has to be executed in order to fetch data, which also means that it will always return the "last" situation.
Materialized view already contains data; in order to make it accurate, you'll have to refresh it. Will it be on demand (only when you say so), or (for example) on commit, it depends on you. So, you'll be able to select records from a materialized view, no matter whether a database link is up or not. However, records you'll get might not be the most accurate.
|
|
|