| Age | Commit message (Collapse) | Author |
|
|
|
client currently doesn't use this but assumes success
|
|
pretty large commit, but it mainly boils to
- reusing the same format clone returns to the client for topo_diff
bad bad code introduced mainly in client side, but server wasn't spared:
- graph/commit_topo__diff massages the links too much - this should not
be there at all, it should be in the correct format to begin with.
server code duplication between clone & topo_diff post processing,
should be factored out
on the good side: single transaction whenever user presses enter, and
the correct place to send back any accumulated diffs (other user
changes).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
}
]
|
|
|
|
|