AuditQuery and relationships



Can relations be queried in the current version (5.x)? For example, would this work:

query.traverseRelation("Child", JoinType.LEFT, "ChildAlias")
					.add("ChildAlias", "name").like(some-value));

Also, not sure if ‘Child’ in this case is the relationship name (in the master Entity), or the child entity name?


AuditQuery and @ElementCollection

I suppose you are talking about Envers. Check out the User Guide for many query examples related to Envers.


Yes, i was not specific enough. This is what I found in the docs you sent the link for:

“The main limitation of the current queries implementation is that you cannot traverse relations. You can only specify constraints on the ids of the related entities, and only on the “owning” side of the relation. This, however, will be changed in future releases.”

BTW, the last sentence was there in version 3.* …


Cam anyone suggest a workaround? I just need to query for the One side properties in a ManyToOne relationship?


Maybe @Naros can help you with that.


Thanks Vlad!
I am not sure, however, how to send a question to a member of this forum directly?


Hi @gbakalar!

In Hibernate Envers 5.x, the only traversal that is currently supported are those that are to-one mappings. We intend to support the to-many association traversal in Hibernate Envers 6.0.

That said, lets assume we have the following mappings:

public class Parent {
  private Integer id;
  private String name;
  @OneToMany(mappedBy = "parent")
  private List<Child> children; 

public class Child {
  private Integer id;
  private String name;
  private Parent parent;

We want to find all the revisions of Child where it has the name C1 and has a Parent with the name P1.

List results = auditReader.createQuery()
    .forRevisionsOfEntity( Child.class, true, false )
    .traverseRelation( "parent", JoinType.INNER )
     // Apply prdicate on the `Parent` entity.
    .add( "name" ).eq( "P1" ) )
     // Apply predicate on the `Child` entity.
    .add( "name" ).eq( "C1" ) )

As you can see from my example, the first argument to traverseRelation is the property name of the attribute you want to traverse relative to the current class as part of the context. In other words, I am saying that we want to traverse the parent property that is in the Child class and then filter on a property in Parent called name with the value of P1.

Hopefully that clears up any confusion.


Thank you very much! This is exactly what I need. To have functional dependencies under control, that is definitely great first step. One thing - how do i query for transitively dependent objects? For example:


Would this work?
List results = auditReader.createQuery()
.forRevisionsOfEntity( Child.class, true, false )
.traverseRelation( “parent”, JoinType.INNER )
.traverseRelation( “grand-parent”, JoinType.INNER )
.add( “gp-name” ).eq( “GP1” ) )

Would this work?


Forgot to ask one more thing - I assume i should be able to set the order to properties that belong to Parent. Is this correct?


@Naros I am getting exception: “… not yet implemented …”. In what exact version is your example supported?



java.lang.UnsupportedOperationException: Not yet implemented for revisions of entity queries
I am using envers version 5.4.1


@Naros - I apologize, but this is urgent and i am not sure if what I need is really supported in 5.4.1?


This is how the implementation looks like:
public AuditAssociationQuery<? extends AuditQuery> traverseRelation(String associationName, JoinType joinType) {
throw new UnsupportedOperationException( “Not yet implemented for revisions of entity queries” );

When you wrote your example, you must have had certain implementation in mind - certainly not the one in 5.4.1 - right?


Yes, so long as the relation is a to-one, you can simply traverse the object-graph as nested as you need and apply the appropriate predicates to filter the results.

I’m not clear on what you’re asking here.

My apologies, you’re correct the RevisionsOfEntityQuery does not yet support this feature; I simply wrote an example to illustrate the syntax and overlooked that. The other two query implementations should work, EntitiesModifiedAtRevisionQuery and EntitiesAtRevisionQuery.

I assume you need to be able to fetch a list of revisions based on predicates rather than knowing the revision numbers ahead of time?


About the order - I need to sort on a property of ‘toOne’ entity.
About the query - Yes, I need a list of revisions filtered by a property of ‘toOne’ entity.

Do you have any idea when will this be available? I would even take ‘code in development’, as long as it can be used for couple of scenarios I need! (that’s how desperate i am :slight_smile:


@Naros - Any hint here?


Is this implemented in Alpha2? If not, is there any info when will it be implemented?


Hi @gbakalar

A number of the new Envers features such as to-many traversal support is not yet in 6.0’s alpha stream as we’ve been more focused on getting hibernate-core stable with all the necessary features. It’s really difficult to flush out and implement behavior in a submodule when the main module does not yet support and implement all the necessary features to build upon in the first place, so its all very much a work in progress stream of changes.

I will need to double check if this is something the feature branch supports. Is the to-one order-by the only sorting you need or do you need sorting on other parts of the domain model, such as the root/parent too?

I’ll take a look and see if we cannot get that implemented in 5.x for RevisionsOfEntity queries to work around the UnsupportedOperationException that the code currently throws. I can’t give you a specific timeline of when I’ll get it working as my time is split among several development projects right now, but I’ll do my best to get it done asap.


I am not sure I understand this question. If I have relationship Child->Parent, and columns Child.c1, Parent.p1, the minimum I would need is sort on either Child.c1, or Parent.p1 (no need together, but just one of them).

Thank you very much!


What I was trying to understand was whether you need to effectively write an order-by fragment that looked something like "ORDER BY child.fieldX DESC, parent.fieldA ASC" . This is what I am not sure if the current implementation is capable of supporting when it comes to traversals.