When a node's has_one association is updated concurrently, it does not respect the one association limit and due to race condition it may result in wrong data. This is very low probable scenario. More details with the spec proving the bug is in below PR
When a node's has_one association is updated concurrently, it does not respect the one association limit and due to race condition it may result in wrong data. This is very low probable scenario. More details with the spec proving the bug is in below PR
Code example (inline, gist, or repo)
https://github.com/neo4jrb/activegraph/pull/1704
Runtime information:
neo4j
gem version: master branch ruby: ruby 3.1.2p20