Feature Requests item #673173, was opened at 2003-01-23 08:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=673173&group_id=40712
Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Really lazy collection loading Initial Comment: It seems that the lazy collection loading implemented in Hibernate loads all the objects in the collection when the collection is accessed (an object is read, or added or removed). That means that it is impossible to have collections that contain many objects. It would be great to have the objects loaded in memory only when they are retrieved from the collection, not all the objects. I suggest the loaded objects are added to the session cache only when they are added or retrieved from a collection, and removed from memory when the session is flushed and if they are no more referenced outside of the collection. Then it would be possible to have collections that contain too many objects to fit into memory. It think that would be a major feature for Hibernate. I need this, to be able to deal with collections that contain several thousands of big objects. Typically I need to manipulate one collection that contains 50000 objects of 6kbyte each. It is currently impossible with Hibernate. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-01-24 01:46 Message: Logged In: NO > the existing collection filter functionality is actually > more efficient and more flexible. I think its underused and I'm > not quite sure why.... Using the standard collections API instead of the Hibernate APIs makes the system less dependent on Hibernate, so it is easier to use without persistence, i.e. most part of a system could run with or without persistence without modifying the source code. This is the Depencency Inversion Principle : my software is more abstract than Hibernate (to my point of view ;)), therefore it should not use the Hibernate API if it were possible. -- Romain ---------------------------------------------------------------------- Comment By: Gavin King (oneovthafew) Date: 2003-01-23 18:54 Message: Logged In: YES user_id=384580 I can *certainly* see the attraction of this. At one stage, we certainly intended to implement this (we were calling it "deep lazy" rather than "really lazy"). However, on the other hand, in most of the use cases I can think of, the existing collection filter functionality is actually more efficient and more flexible. I think its underused and I'm not quite sure why.... ---------------------------------------------------------------------- Comment By: Mark Woon (unkyaku) Date: 2003-01-23 18:16 Message: Logged In: YES user_id=435832 I second this feature. I think this has been brought up before in the mailing list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=673173&group_id=40712 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
