Hi all,
I just wanted to strongly give my vote for including self-relationships into
the next Neo4j release.
I'm the developer of Bio4j project http://www.bio4j.com/ and I have to say
that I really miss the lack of this feature.
There are several cases where not having self-relationships leads
I know this topic has been discussed before[1] and that a trac issue was also
created[2]. I see that a patch was submitted as part of the issue but from
browsing the source code[3] it appears that self-referencing relationships are
still a no-go in Neo4J.
Are there any plans to apply the patch
Hi Shaunak,
As you've noticed, self-referencing nodes have been considered before, and I
remember being perplexed by the lack when I first became a Neo4j user. Changing
the support is simple enough, but there was obviously a conscious design
decision. Why?
Anecdotally (and wiser, longer
Hi,
Another point of contention. For Blueprints Sail, Neo4j is not fully compliant
with the direct mapping between property graph-RDF graph as it doesn't support
self-loops.
https://github.com/tinkerpop/blueprints/wiki/Sail-Ouplementation
Thanks,
Marko.
http://markorodriguez.com
On
Thanks for the explanation, Andreas.
We are modeling the company's infrastructure. Examples of nodes are hosts,
switches, consoles, bootboxes, etc. Examples of relationships are uplink,
boots, etc. An example of a self-referencing node is a console that also
serves as a bootbox for itself.
Hi Shaunak,
Interesting domain. So I guess you'd like a relationship which goes:
+--console--BOOTBOX_FOR--+
| |
+---+
Which I find is an interesting model for your domain. It will match the
physical infrastructure
Where I've wanted self referencing nodes is when mapping a sequence of
user actions:
user clicks button A - [then clicks] - button B - [then clicks] -
button B (again) - [then clicks] - button C - [then ...
Run this over a few 10's of thousands of users (incrementing counts), and
a few dozen
Am 26.04.2011 18:20, schrieb Andreas Kollegger:
What does you model look like, that you expect to require self-referencing?
Oh, I think a loop is just the smallest circle within a graph. So as
Neo4j supports graphs instead of just hierarchical trees it would be a
natural fit ;)
Perhaps it
I've wanted to do similar tracking of paths within a graph, but am not clear
about your approach. Were you creating new relationships between each node
directly to represent an event? I suppose you'd have to add the user id and a
sequence number into each relationship to keep the tracking
In my case I wasn't looking to retrace a specific user's path, but rather
trying to identify popular paths. It was 'quick and easy' to do with a
graph model (except for some confusion about counting self referencing
relationships).
I was, in fact, adding user nodes so I could see the types of
Hi all!
I was playing around with adding support for relationships where the start
node and end node are the same. I managed to come up with a nice litte patch
that adds support for this to the current development version (trunk) of
Neo4j. If anyone is feeling adventurous and want to try it out I
: [Neo4j] Self-referencing relationships anyone?
Hi all!
I was playing around with adding support for relationships where the start
node and end node are the same. I managed to come up with a nice litte patch
that adds support for this to the current development version (trunk) of
Neo4j. If anyone
Very nice. This allows in the meta model to directly implement singleton
classes.
From: tobias.ivars...@neotechnology.com
Date: Fri, 18 Jun 2010 13:23:40 +0200
To: user@lists.neo4j.org
Subject: [Neo4j] Self-referencing relationships anyone?
Hi all!
I was playing around with adding
13 matches
Mail list logo
