Rob,
I hit the same constraint and solved it by introducing a dedicated SELF
relationship directing to a new node but with the same ID property.
Furthermore, I used the indexer capability and only indexed the original
node. Although the new node can have different properties, at least in
my ca
Thanks Anders.
On Wed, Jun 24, 2009 at 10:19 AM, Anders Nawroth
wrote:
> Hi!
>
> > This is probably working as expected but why is this constraint
> necessary?
> >
>
> This works as expected, but I think we have to make this explicit in the
> API docs.
>
> I think there would be a performance hit
Hi!
> This is probably working as expected but why is this constraint necessary?
>
This works as expected, but I think we have to make this explicit in the
API docs.
I think there would be a performance hit for all graph traversals if
relationships to the same node were permitted.
> It is
I just came across the following when I try and link a node to itself:
java.lang.IllegalArgumentException: Start node equals end node
at org.neo4j.impl.core.RelationshipImpl.(RelationshipImpl.java:57)
at
org.neo4j.impl.core.NodeManager.createRelationship(NodeManager.java:280)
at org.ne
4 matches
Mail list logo