Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.mathworks.com!newstransit.mitre.org!news.mitre.org!not-for-mail
From: Peter Sylvester <peters_no_spam_please@mitre.org>
Newsgroups: comp.databases.oracle.server
Subject: Materialized View - Transactional Refreshing
Date: Thu, 09 Sep 2004 10:50:30 -0400
Organization: The MITRE Organization
Lines: 14
Message-ID: <chpqjp$dac$1@newslocal.mitre.org>
NNTP-Posting-Host: peters.mitre.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: newslocal.mitre.org 1094741433 13644 129.83.66.203 (9 Sep 2004 14:50:33 GMT)
X-Complaints-To: news@mitre.org
NNTP-Posting-Date: Thu, 9 Sep 2004 14:50:33 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:224582

I have a materialized view, which due to the complexities, needs to be 
refreshed using the "complete" option (no mview log).

I noticed that the the mview appears to be empty during the refresh 
process (evidently due to a "truncate" being used).

Is there a way to get Oracle to make this transactional (using a delete 
statement), so the mview will always be usable?

I know I can do all this myself, via PL/SQL but would rather use the 
mview technology, if it supports it.

thanks,
--Peter