Database Maintenance Message Persister
Database interface for persisting maintenance messages.
The database model is based on two database tables: the first stores message details such as validity period, system availability, etc and the second stores the translations associated to the messages.
sqlDataSource) cacheTimeout) messageTable) messageColName) messageColSystemAvailable) messageColActive) messageColValidFrom) messageColValidTo) messageColLocation) messageColVersionId) The column must be of an integer type. Usually a long type is used.
messageColRecordInsertionDate) The type of the column must be compatible with a timestamp.
Note that - if configured (see separate property) - user information may also be written to the database at the same time.
messageColRecordInsertionUser) Note that - if configured (see separate property) - the insertion date may alo be written to the database at the same time.
messageColRecordModificationDate) The type of column must be compatible with a timestamp.
Note that - if configured (see separate property) - user information may also be written to the database at the same time.
messageColRecordModificationUser) Note that - if configured (see separate property - the modification date may also be written to the database at the same time.
messageAdditionalWhereClause) The SQL query without an additional where clause is something like
SELECT * FROM message_table WHERE VALID_FROM <= now AND VALID_TO >= now.
The SQL query with an additional where clause
xyz is: SELECT * FROM message_table WHERE VALID_FROM <= now AND VALID_TO >= now AND (xyz).
Note that this where clause may be overridden for the message lookup using property "Message Lookup Additional Where Clause".
translationTable) translationColMessageRef) message-col-name translationColLanguage) translationColMessage) translationAdditionalWhereClause) The SQL query without an additional where clause is something like
SELECT * FROM translation_table WHERE language = 'en'.
The SQL query with an additional where clause
xyz is: SELECT * FROM translation_table WHERE language = 'en' AND xyz. recordModificationUser) additionalInsertData) This allows you to add arbitrary fixed or dynamic values when a new record is created. This is useful if some database fields may not be NULL but are not inserted by this plugin by default.
CautionMake sure to appropriately escape values (e.g. use single quotes around strings). They are used as provided in the SQL insert statements. This allows calling database dependent functions (e.g. in order to get a sequence number, system date, etc).
additionalInsertDataTranslations) This allows you to add arbitrary fixed or dynamic values when a new record is created. This is useful if some database fields may not be NULL but are not inserted by this plugin by default.
CautionMake sure to appropriately escape values (e.g. use single quotes around strings). They are used as provided in the SQL insert statements. This allows calling database dependent functions (e.g. in order to get a sequence number, system date, etc).
type: DatabaseMaintenanceMessagePersister
id: DatabaseMaintenanceMessagePersister-xxxxxx
displayName:
comment:
properties:
additionalInsertData:
additionalInsertDataTranslations:
cacheTimeout: 0
messageAdditionalWhereClause:
messageColActive:
messageColLocation:
messageColName:
messageColRecordInsertionDate:
messageColRecordInsertionUser:
messageColRecordModificationDate:
messageColRecordModificationUser:
messageColSystemAvailable:
messageColValidFrom:
messageColValidTo:
messageColVersionId:
messageTable:
recordModificationUser: Medusa
sqlDataSource:
translationAdditionalWhereClause:
translationColLanguage:
translationColMessage:
translationColMessageRef:
translationTable: