ostrio-Neo4jreactivity

ostrio-Neo4jreactivity copied to clipboard

A call to neo4jCollection.find().fetch() can lead to Meteor constantly refreshing a template

4

You can find a repository with a description and demonstration of this bug here: [https://github.com/blackslate/Neo4j-churn/tree/master](https://github.com/blackslate/Neo4j-churn/tree/master)

blackslate

Meteor.neo4j.collection('players') and the Neo4j browser on port 7474 disagree about the contents of the database

4

I thought that the Neo4j browser running on localhost:7474 and the Meteor-Leaderboard-Neo4j app share the same data in the database. However, I am seeing some evidence that seems to contradict...

blackslate

Steps to reproduce: Clone the repository from [https://github.com/blackslate/Neo4j-call-with-no-callback](https://github.com/blackslate/Neo4j-call-with-no-callback) and run it. Check the output in the browser console. The callback... ``` console.log("Click callback", error, data) ``` ... on line 41...

blackslate

Steps to reproduce: Clone the repository from [https://github.com/blackslate/Neo4jCallback/](https://github.com/blackslate/Neo4jCallback/) and run it. Check the output in the Terminal window. The callback... ``` function testCallback(error, data) { console.log("testCallback on " + environment,...

blackslate

This works as a Publish query callback return value: "MATCH (entrance:Room), (exit:Room) WHERE NOT (entrance)-[:DOOR]->(exit) RETURN entrance" Adding "DISTINCT" makes the query return no entries: "MATCH (entrance:Room), (exit:Room) WHERE NOT...

blackslate

Two nodes with same _id value will crash server

7

If you have two nodes with the same _id ie `Create (a:person {_id:"100"}) Create (b:person {_id:"100"})` it will cause a continual crash meteor until one of the nodes are deleted.

Neobii