CSO_EO_NOTIFICATION

This table is used to store notifications generated by JPA stack for inverse relations that are hidden in JPA side to send to EO (IMConsole) side.

Details

• Schema: FUSION

• Object owner: CSO

• Object type: TABLE

• Tablespace: TRANSACTION_TABLES

Primary Key

Name	Columns
CSO_EO_NOTIFICATION_PK	RECORD_ID

Columns

Name	Datatype	Length	Not-null	Comments
RECORD_ID	VARCHAR2	32	Yes	This is the primary key of the table.
DATE_ADDED	TIMESTAMP		Yes	This is the date that the record was added to the database.
DATE_MODIFIED	TIMESTAMP		Yes	Date record was last modified in database.
TENANT_ID	VARCHAR2	100	Yes	The TenantID or the Reference key of the Repository.
TX_ID	VARCHAR2	32	Yes	The (artificial) UUID of transaction which generated this record. It is recommended to handle all the records of a single transaction together.
TXTIME	NUMBER		Yes	This is the java time in milliseconds (since epoch) when the transaction started. It is NOT stored in MySQL timestamp/datetime to avoid truncation of milliseconds.
DELETED_ENTITY_NAME	VARCHAR2	50	Yes	The EO Entity Name of the Deleted (JPA) Entity.
RELATE_DENTITY_NAME	VARCHAR2	50	Yes	The EO Entity Name of the (JPA) Entity that was related to the Deleted Entity.
DELETED_ID	VARCHAR2	32	Yes	The Primary Key of the (JPA) Entity that was deleted by the transaction.
RELATED_ID	VARCHAR2	32	Yes	The Primary Key of the (JPA) Entity that was related to the Deleted Entity.
REVERSE_RELATION_NAME	VARCHAR2	50	Yes	The Name of the (Exposed) EO Relation (but is Hidden in JPA) that defines the relationship from the Related EO Entity to the Deleted Entity (e.g. Tag.viewsAssignedToTag when Tag is deleted)

Indexes

Index	Uniqueness	Columns
CSO_EO_NOTIFICATION_U1	Unique	RECORD_ID
CSO_EO_NOTIFICATION_N1	Non Unique	TX_ID