You can have any number of easily reachable reference nodes for your
subgraphs. Depends on your use-cases.
If you want to make sure they are uniquely created either create them
upfront, or if you continously do that "as your go, a unique constraint +
merge help you"
create constraint on (r:Reference) assert r.type is unique;
merge (r:Reference { type : "My Reference"}) return r;
Michael
On Sun, Jan 26, 2014 at 10:46 AM, Stefan Armbruster
<[email protected]>wrote:
> In the dark ages before we've had indexing and label, connecting
> everything to the root node was the preferred way to structure the
> graph. Please note in 2.0 the root node (aka reference) node has been
> removed for freshly created databases. However databases migrated from
> earlier versions still have it.
>
> 2014/1/26 Aran Mulholland <[email protected]>:
> > Should all subgraphs of the graph be connected to the root node?
> >
> > Best practice (from my reading) in earlier versions seemed to suggest
> this,
> > now we have labels and indexing this may no longer be the case. Is it?
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Neo4j" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
