Exactly, this is by design. We try to encourage users to use indexes / constraints and business level keys as much as possible and only use node-id's in exceptional cases.
On Tue, Mar 25, 2014 at 11:46 AM, monkeyb <[email protected]> wrote: > Hi Everyone, > > I'm relatively new to node, but went through the training tutorial and > have been working heavily with it the past couple of weeks. My question is > with regards to node id's and relationships. > > I noticed that whenever I query Neo4j, the resultset never returns the > node id's, is this on purpose? The reason I ask is when I try to relate > records, I'm having to rely on other attributes to fetch the nodes in my > MATCH clause, so that I can later use them to build the relation. > > After exhausting google, and noticing that the neo4j training tutorials > never make use of the node id for anything and instead rely on other > identifiers (e.g. movie title, actor name, etc), I've come to the > conclusion/realization that perhaps this is by design, and it's the > responsibility of the DBA to define his own identifiers (and index them) > and not rely on the neo4j node id. > > Am I correct in my assumptions? Your feedback would be much appreciated! :) > > -- > 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/d/optout. > -- 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/d/optout.
