borinquenkid commented on PR #16836:
URL: https://github.com/apache/grails-core/pull/16836#issuecomment-6693145702
@jamesfredley Fixed in 4271678872, on top of 5f502680d3.
`connections { isNull('spouse') }` now tests the relationship's own
property. I reproduced your case first: a node with a `spouse` association and
a relationship entity with a plain `spouse` property made Neo4j reject `NOT
(m_0)-[]->(...)`, because the pattern started at the relationship variable. The
query builder now records the variable of a relationship, and a null test on
that variable is a property test.
`IsNullAssociationSpec` has the feature (`NullTestMate` with a `spouse`
association, `NullTestBond` with a `spouse` string): `isNull` returns the end
of the bond with no `spouse`, and `isNotNull` the other one. The Neo4j core
suite and `codeStyle` pass.
Not changed here: `eq('spouse', ...)` in the same block still looks the
property up on the node, and it did so before this PR too. It is a separate
fix, so I left it out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
