Configure lazy loading in an envers query

[desol4tion]

I need to search an entity for the date d, but i saw that envers returns me my object and charge also all the relationnal objects. My problem is that if i have for example 10000 results, i'm afraid the loading of this relationnal datas take a long time and slow down my query.

So i would like to know if it s possible to specify the way to load data?

Thanks

[adamw]

Hmm all relations are lazy in Envers, even if they are marked as eager in the class. Are you sure you are not accessing the relations and causing them to be loaded?

Adam

[tychinasg]

I don't know shold I create a new discussion or not but anyway. Could relations be non-lazy in envers (some configuration etc.)?

Thanks,

Sergey.

[adamw]

Nope, only lazy currently unfortunately.

Adam

[ndtreviv]

We're in a situation where we're using abstract classes and need to cast to implementations in some areas. Unfortunately, Hibernate's lazy loading doesn't do a great job of proxying abstract classes (ie: it doesn't let you cast to the Impl). This is mostly not an issue because we're not using lazy loading that often in the application. However, envers uses it EVERYWHERE.

We really need envers to support eager loading of objects. Is there a technical reason why this cannot be done?

[adamw]

Well, the queries would get pretty complex to fetch a tree - as the depth may be arbitrary.

Adam

[wgorder]

Is this also true when using the ValidityAuditStrategy?  This lazy loading thing is biting me pretty good in my current project where there are lots of reads and traversals of the audited data.  I am thinking of doing what was suggested in this post. http://stackoverflow.com/questions/7572613/envers-query-returns-a-lazy-result-instead-of-an-eager-one

and mapping the audit tables to regular Entities. I think that the queries are going to look much the same as the table structure really does not change at all when using the validity strategy. Let me also say that this is an awesome framework overall, and has saved me a ton of time on my current project despite this one short coming, but it would be great if some day it were supported.

Thanks,

[marx3]

How would you map audit tables to entities? I've tried to do that. I've added entity which extends my original entity and adds missing fields like revision etc, and map it to table xxx_aud. Hovewer after deploy Hibernate complains about duplicate use of xxx_aud table. So it seems Envers somewhat internally create such entities during startup(?).