Object Relational Mappers: Difference between revisions

From Elvanör's Technical Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Java: Hibernate ==
== [[Hibernate|Java: Hibernate ]] ==


* If you specify a one-to-many or many-to-many mapping, be sure to use the same mapping as the Java collection interface. A Set mapping won't work with a List collection, for example.
* Hibernate is THE reference ORM, the most advanced solution available right now. It is extremely powerful although it takes quite some time to fully learn it (especially its model mappings, which can be complex since they allow almost any kind of mapping).
 
* In Hibernate, lazy loading is on by default for collections. This means the collections are fetched from the database only when they are used (never if they are not used). '''Warning:''' if the loading appears when the Hibernate session is already closed, it will '''fail.'''
 
* If you have an object and a many-to-one mapping on this object (such as Item that belongs to a Category), and you happen to have the ID of the Category but not the associated Java object, in order to store the item on the database the fastest way is to create a new virtual Category and call setID(known_id) on this newly created object. Then, once you save the object, the virtual Category will not be saved (updated) as it already exists.

Latest revision as of 10:44, 19 May 2008

Java: Hibernate

  • Hibernate is THE reference ORM, the most advanced solution available right now. It is extremely powerful although it takes quite some time to fully learn it (especially its model mappings, which can be complex since they allow almost any kind of mapping).