Hi - The issue of unique indices came up several times earlier this summer:
http://neo4j.org/forums/#nabble-td3047393 http://neo4j.org/forums/#nabble-td3148364 http://lists.neo4j.org/pipermail/user/2011-June/009809.html And Mattias created a support ticket: http://help.neo4j.org/discussions/questions/8-re-neo4j-unique-constaint-on-index Has anything become of this? Being able to do a "create or update" on unique properties would be very useful when working with social graph data from Facebook and Twitter. For example, when creating a social app that uses the Facebook graph or the Twitter authentication APIs, it's common to create nodes for all the Facebook friends and Twitter followers so the FB user ID and Twitter username are stored as properties for each "Person" node. If two users have the same friend or follower, the node is already going to exist on insert. Rather than query for the existence of each node, it would be better to just update the node if one already exists with that Facebook ID. Likewise, being able to mark an edge as unique and update it rather than create a dupe if an edge already exists with the same inV, label, and outV (or a unique property) -- for example, you wouldn't want to recreate the edge on the "create or insert" if the node already exists. Thoughts? - James -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/Are-Unique-Indices-in-the-Works-tp3229971p3229971.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
