Here some ideas requiring further discussion:
* Attach a relationship property contributor class
{code}
@RelationshipContributor(AddressRelationship.class)
{code}
* or "fix" a set of property per OO association
{code}
@OneToMany
@JoinTable(name="has_address")
@RelationshipContributor(name="type", value="home", ...)
Set<Address> homeAddress
@OneToMany
@JoinTable(name="has_address")
@RelationshipContributor(name="type", value="work", ...)
Set<Address> workAddress
{code}
One relationship type is split into two OO associations
* or have the generic and the specific relationships in Neo4j but only the specific ones in OO. Each assoc is going to create 2 relationships.
For closed set of properties neo4j Neo4j recommends separate relationships. For open sets like weight, then properties make sense. How to host a weight in OO?
|