Use the
In contrast, the
The two role-dependent usage scenarios for the
From a primary system, to cause persistent events audited by the primary database for replay by secondary database servers.
From a secondary system, to cause events that are notified to event subscribers on the primary system.
Calling the
The actions of the sdsCauseEvent method are summarized in the following table, which lists the contexts in which the event is caused.
Database Role | Transient Target Object | Persistent Target Object, Immediate | Persistent Target Object, Deferred, in Transaction State | Persistent Target Object, Deferred, not in Transaction State |
---|---|---|---|---|
Undefined | Ignored | Exception | Local system | Exception |
Primary | Ignored | Exception | Secondary system | Exception |
Secondary | Ignored | Primary system | Immediately to primary system | Immediately to primary system |
The actions of the
Database Role | Transient Target Object | Persistent Target Object, Immediate | Persistent Target Object, Deferred, in Transaction State | Persistent Target Object, Deferred, not in Transaction State |
---|---|---|---|---|
Undefined | Process only | Local system | Local system | Local system |
Primary | Process only | Primary system | Primary system and secondary | Primary system only systems |
Secondary | Process only | Secondary system | Secondary system and immediately on the primary system | Secondary system and immediately on the primary system |
See also "Causing an Object Event", in Chapter 2.