"Mark Malakanov" <markmal_at_rogers.com> wrote in message
news:xLydnbH1n-Pl8GzfRVn-tQ_at_rogers.com...
>
> Madison Pruet wrote:
> > At a minimun the replication solution should be able to either prevent
> > triggers from firing on the target if it is populated by a replication
> > apply, with the assumption (and policing) that all of the tables
associated
> > with original transaction is replicated as part of that transaction.
>
> Yes, there is a function that should be called in an updateable MV
> target table trigger DBMS_MVIEW.I_AM_A_REFRESH. It returns FALSE if
> trigger is fired by local changes, and TRUE if trigger is fired by
> replication.
>
That's a good feature. But is there a way to prevent the trigger from
firing without having to make the trigger aware of the fact that replication
exists? Otherwise, wouldn't it be difficult to use replication with third
party applications?
Received on Wed Aug 03 2005 - 20:31:38 CDT
