- This topic has 3 replies, 3 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
Is there a way to have a Key class generated for all the hibernate classes? I know they are generated for the composite-id classes but I have so much data and work with detatched sessions so I like to load keys instead of whole classes for relationships much of the time.
Not currently, and there are no plans to support this scenario (unless enough people ask for it!). It is not a common use case. However, with the changes coming down the line, you will be able to more easily alter the mappings after they are generated to support the kind of thing you want.
@support-jeff wrote:
Not currently, and there are no plans to support this scenario (unless enough people ask for it!). It is not a common use case. However, with the changes coming down the line, you will be able to more easily alter the mappings after they are generated to support the kind of thing you want.
One of the reasons I like keys for everything is that I just load the full object and the data footprint is very small. I can basically lazy load across disconnected sessions. The way I do this is have all my hibernated objects extend a BaseKey class. What this allows me to do is implement some standard crud methods for all of my dto’s and not worry about having dao’s for all of them which can be very helpful if you have a lot of objects and don’t want to implement a lot of extra code. All my dao’s extend a base dao with a findByPrimaryKey(BaseKey key), find(BaseKey[] keys), delete(BaseKey key), etc. This gives me a more general way of working with all my data.
Anyway, thanks for checking.
