Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!sn-xit-06!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Sybrand Bakker Newsgroups: comp.databases.oracle.server Subject: Re: Materialized View - Transactional Refreshing Date: Thu, 09 Sep 2004 19:41:15 +0200 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <8b51k0p37eqddbta8bp77sstjb1unie0sm@4ax.com> Reply-To: postbus@sybrandb.verwijderdit.demon.nl References: X-Newsreader: Forte Agent 2.0/32.652 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@supernews.com Lines: 15 Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:224595 On Thu, 09 Sep 2004 10:50:30 -0400, Peter Sylvester wrote: >Is there a way to get Oracle to make this transactional (using a delete >statement), so the mview will always be usable? no. Nor does your suggestion make sense because the mview would be locked during the delete, and delete compared to truncate is pretty inefficient. But if you think a home-grown 'solution' will address your needs, why don't you go ahead knowing better? -- Sybrand Bakker, Senior Oracle DBA