|Oracle® Database Rules Manager and Expression Filter Developer's Guide
11g Release 1 (11.1)
|PDF · Mobi · ePub|
This section describes new features of Oracle Database 11g Release 1 (11.1) and provides pointers to additional information.
The following section describes the new features in Rules Manager and Expression Filter:
Rules Manager — support for Text predicates (CONTAINS) in rule conditions
Text predicates in the rule condition are specified using the CONTAINS operator within the conditions for primitive events.
See Also:See Section 4.4, "Rule Conditions for Text Events"
Rules Manager — support for shareable primitive rule conditions
Rules Manager has provisions to share parts of the rule condition across rules by using references into a common repository of primitive rule conditions. This provides the ability to share primitive conditions, which simplifies the construction of the rule conditions for composite events and also allows for managing them as one logical unit for any modifications made to the shared primitive rule condition.
See Also:See Section 4.6, "Shareable Primitive Rule Conditions"
Rules Manager — support for disabling and enabling rules
Rules Manager lets you add rules to the rule class, but keep them disabled. A rule class table created with
DBMS_RLMGR.CREATE_RULE_CLASS procedure implicitly has an
rlm$enabled column in which to store the status of each rule set to 'Y'. Optionally, a value 'N' can be assigned to this column during the insert of a new rule or update of an existing rule, which will disable the rules until such time these rules in the rule class are set to be enabled.
See Also:See Section 4.5, "Disabling and Enabling Rules"
Rules Manager — support for purging events in development environments
Rules Manager provides a
DBMS_RLMGR.PURGE_EVENTS procedure call to purge any state information and the events from the database prior to deploying an application in a production environment.
Rules Manager — support for
DELETE operations on DML events
When the event structure used for a rule class is defined with one or more table alias attributes, the rule class can be configured to treat all INSERT, UPDATE, and DELETE operations on the underlying tables as the events for which the rules are evaluated. Note that events for
DELETE operations on the underlying tables are only applicable for the rule classes configured for composite events.
See Also:See Section 3.7, "DML and CNF Events"
Rules Manager — support for notifications of data changes within a transaction after the end of a transaction
Rules Manager makes use of the Database Change Notification feature to receive notifications of net data changes (within a transaction) after the end of each transaction. These notifications are used to capture the modified rows or the event data and match them with the rules in the rule class.
Rules Manager — support for collection events and aggregate predicates in rule conditions
Using the new rule condition language extensions, Rules Manager can group a set of events based on certain attributes and test conditions on these collections. The conditions on the collections involve aggregate operators such as
COUNT. The conditions can be specified to operate on collections with moving window semantics.
See Also:See Section 5.6, "Rule Conditions with Collection Events"
Expression Filter — support for Text predicates (CONTAINS) in stored expressions
The Text predicates in the stored expressions are specified using the CONTAINS operator within the SQL WHERE clause syntax.
See Also:See Section 14.2, "Expressions with Text Predicates"