]
Sent: Friday, October 17, 2003 12:09 PM
To: OJB Users List; Thomas Mahler; Armin Waibel
Subject: Re: Wrong class materialized when selecting from
an extent
mapped to a multi-table join
hi justis, wallace,
this problem is caused by Identity#equals noch checking
objectsRealClass
Users List; Thomas Mahler; Armin Waibel
Subject: Re: Wrong class materialized when selecting from an extent
mapped to a multi-table join
hi justis, wallace,
this problem is caused by Identity#equals noch checking
objectsRealClass
. consider the following situation: a select for InterfaceA
fires 2
PROTECTED]
Sent: Friday, October 17, 2003 12:09 PM
To: OJB Users List; Thomas Mahler; Armin Waibel
Subject: Re: Wrong class materialized when selecting from an extent
mapped to a multi-table join
hi justis, wallace,
this problem is caused by Identity#equals noch checking
objectsRealClass
. consider
hi justis,
is this another case of mixing extents and 'super'-references ?
i had a long offline discussion with brendan regarding this topic:
http://article.gmane.org/gmane.comp.jakarta.ojb.devel/3933
http://article.gmane.org/gmane.comp.jakarta.ojb.devel/3920
jakob
Justis Peters wrote:
Hi All!
hi justis,
please send me your testcase.
jakob
Justis Peters wrote:
Hi All!
Just a couple weeks ago I started using OJB, and I am extremely impressed. My gratitude goes to all who put in the work to make it possible.
Upon converting some of the more complicated parts of my object model, I
: Friday, October 17, 2003 6:53 AM
To: OJB Users List
Subject: Re: Wrong class materialized when selecting from an extent
mapped to a multi-table join
hi justis,
is this another case of mixing extents and 'super'-references ? i had a
long offline discussion with brendan regarding this topic:
http
materialized when selecting from an extent
mapped to a multi-table join
hi justis,
is this another case of mixing extents and 'super'-references ? i had a
long offline discussion with brendan regarding this topic:
http://article.gmane.org/gmane.comp.jakarta.ojb.devel/3933
http://article.gmane.org
Hi Jakob,
Thanks for your reply! Yes. What you describe is exactly what I am doing.
I have read your discussion with Brendan, and I understand what you are saying. This
is in direct conflict with what is implied in
http://db.apache.org/ojb/tutorial3.html;, though. The section titled
hi justis,
well, but the sample code does NOT show any extents ;)
i just installed your testcase and will start digging into it.
jakob
Justis Peters wrote:
Hi Jakob,
Thanks for your reply! Yes. What you describe is exactly what I am doing.
I have read your discussion with Brendan, and I
hi justis, wallace,
this problem is caused by Identity#equals noch checking objectsRealClass
. consider the following situation: a select for InterfaceA fires 2 selects
SELECT A0.VALUE_,A0.ID FROM A_TABLE A0
retrieving Table_A objects with ids 1 and 2
SELECT A0.VALUE_,A0.ID FROM B_TABLE A0 INNER
:[EMAIL PROTECTED]
Sent: Friday, October 17, 2003 12:09 PM
To: OJB Users List; Thomas Mahler; Armin Waibel
Subject: Re: Wrong class materialized when selecting from an extent
mapped to a multi-table join
hi justis, wallace,
this problem is caused by Identity#equals noch checking
Hi Jakob,
Thanks for your reply! Perhaps I have some ideas on how we could do this. Here are
two:
Idea 1
--
Join all the columns from all tables in the hierarchy together, and then look to see
which join columns are not null, in order to determine the true subclass
I demonstrate this
12 matches
Mail list logo