Re: Materialized Views: Refreshing same MV by 2 calls to DBMS_MVIEW.REFRESH at the same time.

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Thu, 19 May 2005 09:13:10 +0200
Message-ID: <d6he1p$mpo$1@news6.zwoll1.ov.home.nl>

Noons wrote:
> Frank van Bortel wrote:
>

>>And in addition the my post: an oracle version might be nice. The

>
> latest
>

>>versions have the ability to do a refresh on commit.
>>No calls to DBMS_REFRESH needed.
>>

>
>
> Run that by me again, Frank?
> Didn't see that anywhere. Any info appreciated.
>

Eh? Version, refresh, or refresh on commit?

The discussion was about two (or more) clients starting a search (define search), where OP visioned the refresh of a MV beforehand, triggered by the starting of the search process. DBMS_REFRESH is getting called 'on demand'; aka manually - coded into a packaged proc, called by the search interface.
A MV with refresh on commit (advertised since 8i - working since 9.2) needs no such programming.
Hence my 'no calls needed' - they'll be there, no doubt, or calls to DBMS_MV.refresh.

-- 
Hope this was what you meant,
Frank van Bortel

Received on Thu May 19 2005 - 02:13:10 CDT