Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: user
-
Labels:None
-
Number of attachments :
Description
This is just an improvement of classes to be persisted because Hibernate relies on these methods to work correctly.
Didn't say that this is mandatory but could probably help in some situations.
Well, the thing with these methods and hibernate, is that in some cases you would have to implement them in a "non standard" way. (ie in java, you would usually compare all fields in the equals method, while with hibernate in mind, you would maybe only compare the pk field)
So please describe where/how this would help, with what kind of implementation. I'm not against this at all, but I've never had the time to understand, sit and think about the whole issue, which is why it's as it is at the moment.