Referential integrity

[Craig L Russell]

The JDO 2.0 specification requires that changes to one side of a relationship that is mapped to a single database artifact (e.g. mapping Department.employees and Employee.department to the same column) will affect both sides of the relationship both in the database and in memory.

Craig

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Is there interest in extending this concept to other datastores in which the relationships are not mapped to the same artifact? We might have to provide some metadata aside from "mapped-by" in case the relationships are inverse. Perhaps use an attribute "inverse" at the same level as "mapped-by"?

smime.p7s
Description: S/MIME cryptographic signature