Skip to main content
Skip table of contents

Historization of Data Tables

Information

  • Historization is enabled for all tables.

Details

Details

  • Envers generates a table with the _HIS suffix for each versionized table.
    • The history table of data table DT412 is named DT412_HIS, for instance.
  • A history table contains all columns of the original table as well as the following columns
    • REV = revision
    • REVTYPE REVTYPE = specifies whether something is added (0), refreshed (1), or deleted (2)
  • Each time something is added to, refreshed in, or deleted from the versionized tables, a new line with the respective field status is inserted.
  • The initial object can be identified by its primary key.
  • The modification date is written in the REVINFO Envers standard table ( REVTSTMPcolumn).
  • Via the REV field, the REVINFO table also links all REV fields in the history tables.
  • Each versionized table is identified by the same UUID field, regardless of the actual main field of the database layer.
    • I.e. each _HIS table contains a UUID field with the help of which a specific line in a versionized table can be identified.
    • The UUID fields must exist in any versionized table in the database in order for the historization via Envers to work.

Note

  • If, in the tables which are historized, new columns are inserted which are also historized, the same columns must be inserted in the historization tables.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.