This repository was archived by the owner on Sep 3, 2021. It is now read-only.
Fixes #295: Querying interface @relation fields with non-unique relationship names #366
+7
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #295 resulted from no label being added to the Cypher path pattern for related nodes being matched when querying an interface type
@relation
field. To make the path pattern more specific and prevent matching inappropriate nodes, the interface type name is now added as a label.For example, given the following schema:
And this query over the
tools
interface type@relation
field:Current translation:
Translation with the fix:
In this translation,
tools: [(`product`)-[:`USES`]->(`product_tools`)
becomestools: [(`product`)-[:`USES`]->(`product_tools`:`Tools`)
.