In Envers, retrieve only the most recent revision for all entities of a particular type

[r0nan]

Hello Adam,

I curious about is Envers able to represent some kind of that:

http://opensource.atlassian.com/projects/hibernate/sr/jira.issueviews:searchrequest-fullcontent/temp/SearchRequest.html?jqlQuery=project+%3D+HHH+AND+component+%3D+envers+ORDER+BY+updated+DESC%2C+priority+DESC%2C+created+ASC&tempMax=1000

Since "grouping" or "subselect" not supported.

To be honest my actual problem is to get a Map<Integer, MyClass> where the Integer is the revison number. But since i use the "forRevisionsOfEntity" i get all version, but i only need the most recents! Similary in the link.

Can you please help?

Thanks your time.

[r0nan]

And yeah i know that forEntitiesAtRevision can gives me the recents, but its not able to give me the revisionnumber.

[etellman1]

I had the same question a little while ago.

Adam suggested I submit a feature request, and here it is: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5228

[tspaeth]

I'm currently trying to develop such a feature on the envers source.

Currently - as I am not so deep into Hibernate - I'm having just one problem:

How do I prevent the Envers + Hibernate - stack to replace "e.id" to "table.id and table.REV" during ejb-ql / hql replacements?

The mapping is because of a on-the-fly-generated hbm.xml - file as far as I can see.

But I only need to query for the id with the group by statement.

Any suggestions how to tell Hibernate not to map the key-mapping to both key-elements but only to keep the id - parameter?

Regards,

Thorsten

[adamw]

Maybe you're after e.originalId.id?

Adam

[r0nan]

Can you please let me know if you made it

[tspaeth]

First thanks to Adam for the hint - generally, it seems to do the trick .

But unfortunately the tests currently fail as there is a problem with the hsql-tests against the 1.8.0.2 version dependency (where can I change that? - until now I didn't find the corresponding pom.xml anywhere in the dependency tree). It complaints about not querying for the whole primary key

For the problem: @see http://blog.gmane.org/gmane.comp.java.hsqldb.user/month=20081201 - it might be fixed in the 1.9 - branch.

I switched to mySQL for testing then - but this produces different errors in some tests.

Until now I didn't have the time to look any further due to other projects keeping me busy all the time.

ASAP I'm into it again - I'll let you know!

Thorsten