db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oliver.m...@ppi.de
Subject RE: Identity.realClass set to abstract class?!
Date Thu, 04 Sep 2003 10:52:19 GMT
Hello,

> -----Original Message-----
> From: Armin Waibel [mailto:armin@code-au-lait.de]

> Think you are right, this will be in accordance with
> the definition of 'objectsRealClass'. What about the
> side-effects if we change the matching lines in code
> (without using your proposed field 'lowestKnownClass')?

I assume that my proposed fix will increase the number
of SQL statements needed when navigating through
references.

Assume, for example, that there is one single top-level
class that all other pesrsistence-capable classes
extend.  Then, with my change, resolving a reference will 
result in a search through all tables.

With the current implementation 
PersistenceBrokerImpl.getDBObject,
the table corresponding to objectRealClass will be scanned
first, and afterwards all the others.

It seems that in the current implementation, the meaning
of objectsRealClass is closer to 'lowestKnownClass'.

Olli

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message