Envers: Unidirectional OneToMany without additional audit table?
- yes, you understand the statement from the documentation correctly
- yes, but reading the history of changes of "Phone" would give you subsequent objects which are identical (as only the emp_id would change)
- no, it's not possible to change this behaviour currently. Unless you e.g. change your mapping to a bi-directional one-to-many relation