Hello, I just wanted to jump in
because I'm really not clear on how the queries produced could result in a
cartesian product. Since every level of the graph contains an on
clause that references the table before it, each level of the tree is limited
(by
its
particular join type) and the amo
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
file and an annotated class? By
creating a specific comparison code? By creating the metamodel for both
and comparing them? All that work for an exception...
Gavin King wrote:
I must admit, that this makes sense to *me*
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
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
