This question may reveal some ignorance on my side, but I'm going ahead anyway.

Is there anything which makes it a bad idea to have several different
enums implementing RelationshipType and using these for different
relationships in neo? The reason in my case is that some relationship
types are native to the model (the MusicBrainz model) and ought to
reside in org.musicbrainz.RelationTypes or similar, while other
relationships are specific to my application and not really related to
the model.

The reason I ask is that I don't really understand what an enum is in
Java. If I have

 enum MyRelationshipTypes implements RelationshipType
 {
     CONTAINED_IN, KNOWS
 }

and then rename it to

 enum MomsRelationshipTypes implements RelationshipType
 {
     CONTAINED_IN, KNOWS
 }

will neo treat these as the same or new relationships?

Philip
_______________________________________________
Neo mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to