Mmh,
That is why cascading deletion is not the default on the Java and REST apis. Webadmin was considered to be mostly for testing and introspection.
If you want to reliable address nodes, then I would consider using and index to store your root node and look it up instead of having an absolute id?
Send from mobile.
This sounds almost like being able to set ACL’s on nodes and relationships (except without the users and roles bit).
Why not go all the way and mark them for read, update, and delete ? Throw in an equivalent to “insert” to mean you are not allowed to create a relationship to or from this node. I can’t think of a case where with only one user you’d ever want to take away ‘read’ permissions, so that would be the most basic permission level.
By default node 0 would be read only. All of the other nodes, unless otherwise specified would default to read,update,insert,delete.
The biggest issue I could see with this is the performance overhead of having to check permissions when you are mutating the graph.
Mat,
Could you please raise a feature request for this?
Send from mobile.
--
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 neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the Google Groups "Neo4j" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/neo4j/Sb2ANlJtLDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to neo4j+un...@googlegroups.com.