Is using a tree with a counter on the root node, to be referenced and incremented when creating new nodes, a viable way of managing unique IDs in Neo4j? In a previous question on performance on stackoverflow (Neo4j merge performance VS create/set <http://stackoverflow.com/questions/30403504/neo4j-merge-performance-vs-create-set#>), the approach was described, and it occurred to me it may suggest a methodology for unique ID management without having to extend the Neo4j database (and support that extension). However, I noticed this approach has not been mentioned in other discussions on best practice for unique ID management (Best practice for unique IDs in Neo4J and other databases? <http://stackoverflow.com/questions/23870292/best-practice-for-unique-ids-in-neo4j-and-other-databases> ).
Can anyone help validate or reject this approach? Thanks! -- 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.
