README.md

Spring Data Envers (Hibernate Envers)

The Envers project aims to enable easy auditing of persistent classes. All that you have to do is
annotate your persistent class or some of its properties, that you want to audit, with @Audited.
For each audited entity, a table will be created, which will hold the history of changes made to the
entity. You can then retrieve and query historical data without much effort.
Similarly to Subversion, the library has a concept of revisions. Basically, one transaction is one
revision (unless the transaction didn't modify any audited entities). As the revisions are global,
having a revision number, you can query for various entities at that revision, retrieving a (partial)
view of the database at that revision. You can find a revision number having

Resources

• Spring Docs
• Hibernate Docs

Usage

Try to APIs on Postman

Note

If you add Hibernate Envers to existing Hibernate Entities, you need to write a custom migration script.

DO
$$
    DECLARE
        USER_TABLE_RECORD RECORD;
        HISTORY_INFO_ID   INTEGER;
    BEGIN

        TRUNCATE TABLE HISTORY_INFO CASCADE;

        FOR USER_TABLE_RECORD IN SELECT * FROM USERS

            LOOP
                HISTORY_INFO_ID := NEXTVAL('HISTORY_INFO_SEQ');

                INSERT INTO HISTORY_INFO(ID, DATE)
                VALUES (HISTORY_INFO_ID, USER_TABLE_RECORD.CREATED_DATE);

                INSERT INTO USERS_HISTORY(ID, HISTORY_INFO_ID, TYPE, FIRST_NAME, LAST_NAME)
                VALUES (USER_TABLE_RECORD.ID, HISTORY_INFO_ID, 0, USER_TABLE_RECORD.FIRST_NAME, USER_TABLE_RECORD.LAST_NAME);
            END LOOP;

    END
$$;