activegraph
activegraph copied to clipboard
neo4jrb
An active model wrapper for the Neo4j Graph Database for Ruby.
I've got an exception popping up during a transaction and it looks like neo4j is throwing another exception while trying to process that one. It looks like a simple method...
Just putting this up to track the fact that cypher has deprecated the `CREATE UNIQUE` clause in favor of accomplishing the same thing using `MERGE` (see: http://neo4j.com/docs/developer-manual/current/cypher/clauses/create-unique/). I imagine this...
This PR adds bang setters for simple (non-ActiveRel) associations which raise an error if the association fails to persist (without an extra DB call). In my testing, creating an association...
If I code; ``` r = Rel.where(from_node: node1, to_node: node2).first r.update_attributes!(...) ``` I'm getting an error at the first line and the problem is; The parsed cypher is: `MATCH(...) WHERE...
This would be similar to `db:reset`. Could this be handled by wrapping [database_cleaner](https://github.com/DatabaseCleaner/database_cleaner) which has support for Neo4j? ### Runtime information: Neo4j database version: neo4j gem version: 9.0.5 neo4j-core gem...
Additional information which could be helpful if relevant to your issue: ### Code example (inline, gist, or repo) ```ruby User.where(age: 20).limit(10).skip(1).created_activities(:activity, :rel).pluck(:activity) ``` ### Runtime information: Neo4j database version: `neo4j`...
ActiveNode could be closer to ActiveModel by implementing a `delete` method similar to ActiveRecord, that just deletes a node and does not trigger callbacks. Alternatively a short note in the...
During an environment deployment we had an issue wherein a migration returned as successful but actually failed to create a constraint in the database. The migration ran for 180 seconds...
I'm doing a few benchmarks for my app using [`derailed`](https://github.com/schneems/derailed_benchmarks) gem. I noticed that `neo4j` is including `neo4j-rake_tasks`, that is useful for development, but I don't think it's very useful...
Would be a nice feature, but it would also help improve compatibility with gems which generate migrations (see [this issue](https://github.com/neo4jrb/devise-neo4j/issues/33#issuecomment-355034728) in the `devise-neo4j` repo)