Hi @Naros, we use envers property org.hibernate.envers.do_not_audit_optimistic_locking_field as false for saving version into audit table. Here by setting this property to false, I predict When no other columns are changed also, there will be an entry into audit table. We got two rows of an audit table with same version. But is it possible to have two rows with same version due to this property setting? Thanks in advance.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Envers version field is nul | 7 | 3373 | April 15, 2020 | |
| Hibernate envers issues | 4 | 2324 | April 12, 2018 | |
| Using Envers to track only the fact that a column has changed | 4 | 4401 | January 22, 2018 | |
| Hibernate Envers audit oneToMany side too, even if it has no changes | 3 | 6310 | June 21, 2019 | |
| Envers behviour inconsistent when @Version field auditing is enabled | 6 | 728 | May 6, 2022 |