We're updating the issue view to help you get more done. 

Model graph relationship with properties

Description

Here some ideas requiring further discussion:

  • Attach a relationship property contributor class

    1 @RelationshipContributor(AddressRelationship.class)
  • or "fix" a set of property per OO association

    1 2 3 4 5 6 7 8 9 @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

    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 recommends separate relationships. For open sets like weight, then properties make sense. How to host a weight in OO?

Environment

None

Status

Assignee

Unassigned

Reporter

Davide D'Alto

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major