| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
if at all, not a confirm dialog)
|
|
|
|
|
|
|
|
cross the wire
|
|
|
|
Code is ugly on too many counts, but mainly:
1. repeats local change twice, once for temp and once for non-temp that
goes through server.
2. handles topo_diff reply expecting a single id instead of having a
general topo_diff reply handler that will take care of it, possibly
hanging a callback on it for graph update.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
copied from update_node)
Adds a copied TODO for handling id changes (i.e. same problem on nodes)
plus a new TODO for a fake API (relevant to both nodes and links)
|
|
Tested for name changes only, with the next commit's client side change.
Notes:
uses more than a single query to change each link's name. Since we use
label's, and neo4j is finniky about them, we must:
1. create a new link with copied properties (for future proofing, we use
none at the moment)
2. delete the old link.
Cannot do those in the same statement, the following results in a Neo4j
error:
match a-[l]->b create a-[l2:Poo]->b set l2=l delete l
"errors": [
{
"code": "Neo.DatabaseError.Statement.ExecutionFailure",
"message": "Relationship 13 has been deleted",
"stackTrace": <snip>
}
]
|
|
|
|
|
|
name - name & __type; need to fix client but good enough for now
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
