Alex Roytman wrote:
> Do you plan to enhance the way horiz. refs and collections are stored and
> resolved?
We plan to add support to allow a subclass to narrow the type of
references to other horizontally-mapped classes.
-Patrick
This is a discussion on Is there any advantages in horizontal mappings? - Weblogic ; Please correct me if I am wrong but it appears that horizontal mapping as i= s have very little use over completely independent classes extending pure abstract class (no fields). I think so because all references or collection= s which ...
Please correct me if I am wrong but it appears that horizontal mapping as i=
s
have very little use over completely independent classes extending pure
abstract class (no fields). I think so because all references or collection=
s
which involve horizontally mapped superclass are handled as PC collections
anyway. Two completely independent classes will be handled the same way.
There might be some optimization in case of horizontal mapping which are no=
t
apparent over PC references/collections. Please tell us about it.
Do you plan to enhance the way horiz. refs and collections are stored and
resolved?
For example it would be nice if you stored OID not as class name plus
serialized OID in one column but as class indicator (many people use
integer) in one column and OID in the other and not serialized but column
per oid field. This will allow more efficient queries in Kodo and directly
from SQL because as is serialized OID with class name can not be effectivel=
y
queried in SQL
Alex Roytman wrote:
> Do you plan to enhance the way horiz. refs and collections are stored and
> resolved?
We plan to add support to allow a subclass to narrow the type of
references to other horizontally-mapped classes.
-Patrick