All of my persistent classes inherit from a common (non-persisted) superclass which declares an id field (long). The equality semantics for our schema are such that if two objects have the same id, they are "equal" in the Java sense.
So, I wrote equals() and hashCode() based only on the id field. If I understand correctly, any time a proxy instance is created, the id field will be known before initialization (it is the primary key). If this is the case, is there any way I can get hibernate to *not* auto fault-in (initialize) the object simply because I called .equals() on it? We'd like to use objects as Hashtable keys without always faulting them in. Thanks! - a -- "protect" is a propaganda word ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
