Hardik Joshi
Hardik Joshi
Fixes #301 The sparse fieldsets is not filtering relationships. Currently if we specify any attribute and/or relationship in `fields` param, it works correctly on attributes but the not on relationships....
When we initialize two nodes with mentioning relationship on both side, It creates two identical relationship between these two nodes. Should it only create one relationship instead? ### Code example...
### Code example (inline, gist, or repo) Failing specs to demonstrate the issue https://github.com/neo4jrb/activegraph/pull/1690 ### Runtime information: neo4j gem version: [11.3.1](https://rubygems.org/gems/activegraph/versions/11.3.1) neo4j database version: `4.4.11 Enterprise `
Hello Everyone, I am using [echo/client.rb example](https://github.com/socketry/async-io/blob/main/examples/echo/client.rb) without having `Async` wrapper call around it. I am aware some of this gem's feature like `SharedEndpoint` and `Trap` won't work without Async...
#206 has a failing test describing the case where the connection is not returned properly back into pool, when a thread is interrupted or encounters error.
From [change log of 5.23](https://neo4j.com/release-notes/database/neo4j-5/) ``` Naked CALL subquery (no parameters), e.g CALL {…} is deprecated and should be replaced with CALL() {…}. ``` Find all use of `CALL {}`...
Issue: `ActiveGraph::Core::Query#return` method accepts variable length arguments, but fails when `nil` is present in this argument. the same issue is present with `order` clause e.g. ``` core_query_obj.return('result_node_1', 'result_node_2').first # works...