<disclaimer>I sent this to the list yesterday but I never received it; I also
never saw the emails for my commits. So here is another try, please forgive
me if it is only a problem on my end:</disclaimer>
I have added some support for a certain type of object-relational mapping that
includes a class hierarchy to the OM/Peer model. Here is a short description.
Note that it has not been tested much, I expect it to be tested more
extensively early next week.
John McNally
commit message:
Added support for a table to map to multiple objects. This kind of mapping
will occur for a table in which a column is specified as an inheritance
column (inheritance="single"). Then the column should either contain the
available classnames or keys that match attributes given in the schema
<column ... inheritance="single">
<inheritance key="1" class="Foo"/>
<inheritance key="2" class="Bar" extends="Foo"/>
</column>
These additions support the one table per class hierarchy type of
object-relational mapping. Currently only a single class type can be
represented per row (a row could represent a Customer or an Employee.
But a person who is both a customer and an employee will require two
rows in the table. Other possible arrangements could exist, but more
code will need to be written to support them.
These changes have been tested only that they compile and do not appear
to affect objects that do not use the new functionality.
As a part of this addition the methods in the Peers were refactored in
such a way as to better support the requests of users who want methods
that are much more efficiently implemented without object generation.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
