Sets or changes system information kept by the Rules Engine by (re)setting the value of the specified property. To retrieve the existing value of a property, use the GetProperty method.
Syntax
SELECT RulesEngine.SetProperty(
property
, value
)
or
INVOKE RulesEngine.SetProperty WITH
SELECT property
, value
FROM ...
The required and case-insensitive property must be one of the properties listed in the table below. Many of these properties have an equivalent Deployment Configuration parameter.
The required and case-sensitive value is the value that the property must be set to.
Example
SELECT RulesEngine.SetProperty( 'MaxConstraintDepth', 75 )
The following properties are available for use with the SetProperty method. All properties except "EndUserMsgs" are associated with a Deployment Configuration parameter.
Property
|
Description
|
AllowSetManipulations
|
Specifies whether manipulations are to be handled set-oriented or not. The syntax is:
SELECT RulesEngine.SetProperty ('AllowSetManipulations', 'Yes|No')
|
BatchLogLevel
|
Specifies the log level of batch jobs. Possible Values are: No Logging, Debug, Information, or Error). The syntax is:
SELECT RulesEngine.SetProperty('BatchLogLevel', '<log level>')
|
EndUSerMsgs
|
Specifies whether the end user message mode is to be enabled. disabled, or reset to to the value it had when the application was started. The syntax is:
SELECT RulesEngine.SetProperty
('EndUSerMsgs', 'Yes|No|Reset')
|
LockForeignKeys
|
Specifies whether the parent record must be locked when foreign keys are checked. The syntax is:
SELECT RulesEngine.SetProperty ('LockForeignKeys', 'Yes|No')
|
LockParentOnSeqno
|
Specifies whether parent records must be locked when child records are being entered. The syntax is:
SELECT RulesEngine.SetProperty ('LockParentOnSeqno', 'Yes|No')
|
MaxConstraintDepth
|
Specifies the maximum number of recursions that may occur when constraints are checked. This must be a positive number. The syntax is:
SELECT RulesEngine.SetProperty ('MaxConstraintDepth', '<max number>')
|
MaxDriverConditions
|
Specifies whether or not extra conditions should be added to the main query. The syntax is:
SELECT RulesEngine.SetProperty (MaxDriverConditions', 'Yes|No')
|
NumberOfUpdateColumns
|
Specifies what the UPDATE statements generated by USoft Developer will look like. For tables with column counts lower then this value the conceptual processor will generate UPDATE statements that update all columns of the table. This has the advantage that RDBMS cursors created for these statements can be reused. This increases performance.
If the column count of a table is equal to or higher than this value, UPDATE statements on this table will only update the columns actually updated. The syntax is:
SELECT RulesEngine.SetProperty ('NumberOfUpdateColumns', '<value>')
|
RecordFactsCacheSize
|
Sets the value for the RecordFactsCacheSize deployment configuration property. A positive value for this parameter sets the cache to that size, a value of -1 turns off the cache. The syntax is:
SELECT RulesEngine.SetProperty ('RecordFactsCacheSize', '<max no of entries in the cache>')
|
ShowMiddlewareErrors
|
Specifies whether or not middleware error messages are to be displayed. The syntax is:
SELECT RulesEngine.SetProperty ('showMiddlewareErrors', 'Yes|No')
|
ShowRdbmsErrors
|
Specifies whether or not RDBMS error messages are to be displayed. The syntax is:
SELECT RulesEngine.SetProperty ('showRdbmsErrors', 'Yes|No')
|
TempTablesAtOwner
|
Specifies whether temporary tables are to be created in the owner's schema. The syntax is:
SELECT RulesEngine.SetProperty ('TempTablesAtOwner', 'Yes|No')
|
UniqueKeyCheck
|
Specifies whether the Rules Engine must perform unique key checks in the case of non-manual data entry, for example sql-script() functions. The syntax is:
SELECT RulesEngine.SetProperty ('UniqueKeyCheck', 'Yes|No')
|
UpdateSupertypeOnInsert
|
Specifies whether inserting a subtype for an existing supertype must be considered as an UPDATE on the whole constellation. The syntax is:
SELECT RulesEngine.SetProperty ('UpdateSupertypeOnInsert', 'Yes|No')
|
WaitForLock
|
Specifies the behavior of your application when lock statements are sent to the database. The syntax is:
SELECT RulesEngine.SetProperty ('WaitForLock', 'wait|nowait|default')
|
See Also
RulesEngine.GetProperty
RulesEngine Internal Component
Internal Components
|