As the Hibernate devs will often sarcastically remind you, the dev list is NOT
a user forum. Check hibernate.org for a link to the forums, where people are
more apt to help.
That said, access to mapping information for a persistent class is usually done
through the SessionFactory. In Hibernate
hat: if
you can suggest a better way of doing this, or a way to split up the above
queries when loading the graph, which avoids n+1 selects, please point us to
the documentation.
Thanks,
Jordan
-Original Message-
From: Adrian Ridner
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday,
February 09,
M
Subject: RE: [Hibernate] Is it worth contributing this code or posting it
somewhere?
Correct. This is a current limitation that will be solved “soon”.
Meaning right after 3.0 final release. Its fairly straightforward.
----
*F
Wouldn't it make sense for it to throw an exception if the mappings are
different, otherwise who cares? In migrating, if one
makes a mistake it would be good to know - "xxx has two different
configurations" and not pick one which has precedence (I'm coming from the
standpoint of someone who may
Well I guess if it's too difficult or slow to compare them, then issuing a
warning along with the action Hibernate took (configurable somewhere) seems
fine.
-JL
- Original Message -
From: "Emmanuel Bernard" <[EMAIL PROTECTED]>
To: "Gavin King"
Yeah you have to click on the 3.1 beta 1 link in that gray box on
http://www.hibernate.org/255.html
to get to the sf download.
http://sourceforge.net/project/showfiles.php?group_id=40712&package_id=141977
hasn't been
updated yet.
- Original Message -
From: "Xavier Poinsard" <[EMAIL P
