On Fri, Nov 20, 2009 at 12:19 PM, Mattias Persson <[email protected]> wrote: > 2009/11/20 Mattias Persson <[email protected]>: >> 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. > And I should add: so therefore it's not a good idea to store node ids > as properties, in any such case use a relationship instead.
Ok thank you. So, when i run my app : - I check if the referenceNode have a relationship of type "configuration", "index", whatever i want. (traverser depth_one ?) - if yes, i can retrieve all the info i need on thoses various node. - if no : i create one of my "system" node. create a relationtype according type from referencenode to my new systeme node - and, finally : i do whatever i want with thoses new nodes :) The question is : isn't it much more simple to just store nodeID ? :) -- Ker2x _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
