ZCA_ES_HIER_SNAPSHOTS

This table is used to store the hierarchy snapshots

Details

  • Schema: FUSION

  • Object owner: ZCA

  • Object type: TABLE

  • Tablespace: FUSION_TS_TX_DATA

Primary Key

Name Columns

ZCA_ES_HIER_SNAPSHOTS_PK

HIER_SNAPSHOT_TABLE_NAME

Columns

Name Datatype Length Precision Not-null Comments
HIER_SNAPSHOT_TABLE_NAME VARCHAR2 30 Yes the primary key, which is the name of the dynamic table that has the snapshot
META_MODEL_VERSION_UUID VARCHAR2 36 Yes the uuid of the meta model that this snapshot was created for
HIERARCHY_TYPE_NAME VARCHAR2 30 Yes the name of the hierarchy type that this snapshot is for
SNAPSHOT_NUMBER NUMBER 3 Yes the number of this snapshot, either 0, 1, 2, or 3
SNAPSHOT_TIMESTAMP TIMESTAMP Yes the timestamp of immediately prior to when this snapshot was taken
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row.
OBJECT_VERSION_NUMBER NUMBER 9 Yes Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
USER_LAST_UPDATE_DATE TIMESTAMP Disconnected Mobile: indicates the date and time of the last update of the row. This value is different from LAST_UPDATE_DATE if the update originally happened in a different database (i.e. a different mobile database or the server).

Indexes

Index Uniqueness Tablespace Columns
ZCA_ES_HIER_SNAPSHOTS_PK Unique FUSION_TS_TX_DATA HIER_SNAPSHOT_TABLE_NAME
ZCA_ES_HIER_SNAPSHOTS_U1 Unique FUSION_TS_TX_DATA HIERARCHY_TYPE_NAME, SNAPSHOT_NUMBER