When using the web admin console after doing an operation I get a summary like
1 node inserted
2 relationships inserted
1 node deleted.
It would be good to have the REST endpoint be able to return summary of operations completed at present one has to return the nodes inserted to know an insert has occurred.
When doing a request over the network often it is a good idea to minimize the data response size. A quick summary would help with this.
Sounds legit, however mostly applicable for the /db/data/cypher ? Feel free to enhance that endpoint!
+1 for Cypher, I wanted to have this come back as one of the functions for AnormCypher, but found it wasn't available.
Also +1 Cypher. A unified interface returning one data with different syntax is more than reasonable i think, it's a must.
This will be most probably be part of the query statistics like time, execution plan etc.
@vantonio Could you elaborate a bit on the expected behavior you'd like to see ?
If we get this back from the REST API, then drivers can republish it into other stats pipelines within our own apps, like http://miniprofiler.com/. Neo4jClient already exposes event hooks that allow integration with profilers like this, but we don't have the same richness of data that the console exposes.
The use-case here is beyond debug, likely UAT or similar, and potentially even production, so we won't want full query plans on every request. (But might on some.)
I would suggest doing this by identifying a request's Accept header:
a) on a request with header "Accept:application/json", we would return what we are returning now;
b) on a request with header "Accept:application/meta+json", we would return our original json plus a "status" array with "nodes_created", "time_executed", "node_deleted" etc.
This is now implemented in the Neo4j Browser, and available via the Transactional Endpoint, implemented in 2.0+.