The best way to achieve that is to create relationships to those nodes... such as
ReferenceNode --[CONFIGURATION]--> ConfigurationNode ReferenceNode --[INDEX]--> IndexNode a.s.o. That's more of a neo-style-approach. The node ids persist over time until they are deleted and deleted ids may be reused in the future. 2009/11/20 Laurent Laborde <kerdez...@gmail.com>: > Friendly greetings ! > > I'm a new user and... not a coder. I'm sysadmin & Postgresql DBA at > http://www.over-blog.com/ > > I'm confused about the documentation. > I'm not 100% sure that a nodeID persist over time, restart, update. > Can you tell me please ? > > I'd like to store in the referenceNode some information like : > - "MyConfigurationNode" : NodeID > - "MyIndexNode" : NodeID > - "LastUpdatedNode" : NodeID > - "SequenceStoreNode" : NodeID > - etc ... > > And to be able to retrieve some various custom information at startup, > easily, just by reading the referenceNode. > Will it work ? > > Thank you > > -- > ker2x > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Neo Technology, www.neotechnology.com _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
