Uploaded image for project: 'Hibernate ORM'
  1. HHH-9062

Validity audit strategy: end revision timestamp is not stored in tables for joined subclasses

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 4.2.10, 4.3.11, 5.0.10, 5.2.1, 5.2.2
    • Fix versions: 6.0.0.Alpha1
    • Components: hibernate-envers
    • Labels:
      None
    • Requires Release Note:
      Affirmative
    • Last commented by a user?:
      true
    • Sprint:

      Description

      I use envers with the validity audit strategy where the end revision is stored for fast lookups. Additionally, I store the end revision timestamp for an useful partitioning scheme as described in the envers user guide.

      The problem is, that the end revision timestamp is not stored in tables which are used by entities which are mapped with the joined-subclass mapping strategy. Of course, the end revision must not be stored in such tables, because they are joined with the superclass table where the end revision is stored. However, the end revision timestamp is necessary for partitioning.

        Attachments

          Issue links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: