Re: [Neo4j] User Digest, Vol 51, Issue 110

2011-06-18 Thread Mattias Persson
Have you got any use case where this would be a necessary thing to have and where the current model wouldn't suffice? Just curious. 2011/6/17 Aniceto Pérez y Madrid ape...@innovasoftps.com I agree,a Node is something that has 2 (user managed) fields: Relationship[] Property[] and a

Re: [Neo4j] User Digest, Vol 51, Issue 110

2011-06-18 Thread Mattias Persson
Sorry, disregard my question, I read your example in another mail now. 2011/6/18 Mattias Persson matt...@neotechnology.com Have you got any use case where this would be a necessary thing to have and where the current model wouldn't suffice? Just curious. 2011/6/17 Aniceto Pérez y Madrid

Re: [Neo4j] User Digest, Vol 51, Issue 110

2011-06-17 Thread Aniceto Pérez y Madrid
I agree,a Node is something that has 2 (user managed) fields: Relationship[] Property[] and a Relationship is something that has 2 (user managed) fields: Node[2] Property[] and currently Property has two fields String key Object value where Object can be a scalar or array of basic types:

Re: [Neo4j] User Digest, Vol 51, Issue 110

2011-06-17 Thread Peter Neubauer
Aniceto, introducing real Node and Relationship links as fields on Nodes and relationships would essentially blur the distinction between Nodes, Properties and Relationships, and let you treat the graph as a Hypergraph. We find that model too abstract and hard to deal with the edge cases of these