:36 +0200
To: user@lists.neo4j.org
Subject: Re: [Neo] Indexing Relationships?
There is no indexing component for Relationships and there has never
been
one.
The interesting question that you should have asked is: _will_ there
ever
be
one.
The answer to that question is: maybe
: tobias.ivars...@neotechnology.com
Date: Sat, 15 May 2010 13:32:36 +0200
To: user@lists.neo4j.org
Subject: Re: [Neo] Indexing Relationships?
There is no indexing component for Relationships and there has never
been
one.
The interesting question that you should have asked is: _will_
:32:36 +0200
To: user@lists.neo4j.org
Subject: Re: [Neo] Indexing Relationships?
There is no indexing component for Relationships and there has never been
one.
The interesting question that you should have asked is: _will_ there ever
be
one.
The answer to that question is: maybe
On Tue, Jul 7, 2009 at 5:15 PM, Symeon (Akis)
Papadopoulospapa...@iti.gr wrote:
Johan Svensson wrote:
What we keep forgetting is that the graph already is the index. A well
designed graph will often check if a specific relationship exist
between two nodes just as fast as asking an already
Was that what you meant?
My interpretation of Symeons request was an index from
(RelationshipType,Node,Node) to Relationship, which in my opinion would be
much more useful than a simple index from (String,primitive) to
Relationship, which is how the node indexes work.
That was exactly
2009/7/7 Symeon (Akis) Papadopoulos papa...@iti.gr:
Was that what you meant?
My interpretation of Symeons request was an index from
(RelationshipType,Node,Node) to Relationship, which in my opinion would be
much more useful than a simple index from (String,primitive) to
Relationship, which
On Tue, Jul 7, 2009 at 10:12 AM, Symeon (Akis) Papadopoulos
papa...@iti.grwrote:
Perhaps the lookup method should have an additional argument specifying
whether the relationship is directed or not.
Good point, but I think it's better to add a specific method for that kind
of lookup:
Hello,
We have discussed this and given it some thought before. I think
having a global index on (node1,node2,relationship) will not work
well. Just managing that index will slow down relationship create and
delete a lot.
What we keep forgetting is that the graph already is the index. A well
Johan Svensson wrote:
Hello,
We have discussed this and given it some thought before. I think
having a global index on (node1,node2,relationship) will not work
well. Just managing that index will slow down relationship create and
delete a lot.
I agree. That's why, as Tobias noted in a
Hi Symeon,
so, what you are saying is that you would like to have the possibility
to set indexes on relationships and their properties just like on the
nodes as in http://components.neo4j.org/index-util/ ?
I guess that would be easy to do, or you could do it yourself by
looking at the index-util
Hi!
As the relationships are a core strength of neo4j, this would be a nice
addition to the index API.
In the current IMDB example data model the roles are modeled as
relationships and at the moment not searchable (which they really should
be). So I have a use case for this!
There are
11 matches
Mail list logo
