Use the SAVE PROPERTY statement to set properties for a current active transaction in the replica database that is saved for propagation to the master database.
The SAVE PROPERTY statements can be executed only in a replica database. The property values can be read in the master database.
The statements of the transaction in the master database can access these properties by calling the GET_PARAM() function. Properties are only available in the replica database that apply to the following statement:
MESSAGE APPEND unique‑message‑name PROPAGATE TRANSACTIONS WHERE property > 'value‑string'
When the transaction is executed in the master database, the saved properties are placed on the parameter bulletin board of the transaction. If the saved property already exists, the new value overwrites the previous one.
▪ The SAVE DEFAULT PROPERTY statement defines default properties that are saved to all transactions in the current connection.
▪ The SAVE DEFAULT PROPAGATE PROPERTY statement saves default transaction propagation criteria. For example, you can use this statement to set the propagation priority of transactions that are created in the current connection.
The SAVE DEFAULT PROPAGATE PROPERTY statement can be used on connection level to append all MESSAGE APPEND PROPAGATE TRANSACTIONS statements with a default WHERE clause (if those statements do not already have a WHERE clause). If a MESSAGE APPEND PROPAGATE TRANSACTIONS statement does have a WHERE clause, the default clause that is set with the DEFAULT PROPAGATE PROPERTY is ignored for that statement.
▪ A property or a default property can be removed by re-saving the property with value string NONE.
Return values
Error code
Description
13086
Invalid data type in a parameter.
Result set
The SAVE PROPERTY statements do not return a result set.
Examples
SAVE PROPERTY conflict_rule VALUE 'override'
SAVE DEFAULT PROPERTY userid VALUE 'scott'
SAVE DEFAULT PROPERTY userid VALUE NONE
SAVE DEFAULT PROPAGATE PROPERTY WHERE priority > '2'