, loldrup lold...@gmail.com wrote:
I'm trying to figure out how to model the world most flexibly (okay, so
I'm
sticking to modelling organisations for now, but still). My main problem
seems to occur when I want to allow the model to naturally expand in
complexity. Say we have the following
Subtyping of relationship types sounds like the cure to my problems.
When creating a relationship IS_A_JANITOR_OF, will a corresponding
relationship type IS_A_JANITOR_OF-relationship-type automatically be
created?
If I have a simple relationship can I then ask which relationship types it's
type
Hmm.. Which book would you recommend me to read?
Jon
On Sep 24, 2011 7:55 PM, Thad Guidry [via Neo4j Community Discussions]
ml-node+s438527n3364798...@n3.nabble.com wrote:
Quite wrong.
IS_JANITOR_OF will stick you into a boxed node ordinal.
What you really want when modeling the world is
What if:
Joe WORKS_AT the school
Joe WORKS_AS a janitor
The school HAS_A janitor
How do I denote that Joe works as I janitor at that exact school?
Do you see other problems in the notation above?
Also, thank you very much for your thought inspiring reply!
Jon
On Sep 24, 2011 7:55 PM, Thad
Niels Hoogeveen wrote:
I just posted an example on how to use HyperRelationships:
https://github.com/peterneubauer/graph-collections/wiki/HyperRelationship-example
This link now gives 404. Does it have a new address? If so, what is it?
Jon
--
View this message in context:
I'm trying to figure out how to model the world most flexibly (okay, so I'm
sticking to modelling organisations for now, but still). My main problem
seems to occur when I want to allow the model to naturally expand in
complexity. Say we have the following relationship:
Joe is a janitor at the
How come relationships are strongly typed while every node is just a generic
node? Example:
import org.neo4j.graphdb.RelationshipType;
public enum TaxonomyRelationshipTypes implements RelationshipType {
KNOWS
}
...
Node node1 = graphDb.createNode(); //just a generic node, apparently
Node
7 matches
Mail list logo
