-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The connection to a to-1 union does not check whether only one node is actually connected. #4424
Comments
Many thanks for raising this bug report @AccsoSG. 🐛 We will now attempt to reproduce the bug based on the steps you have provided. Please ensure that you've provided the necessary information for a minimal reproduction, including but not limited to:
If you have a support agreement with Neo4j, please link this GitHub issue to a new or existing Zendesk ticket. Thanks again! 🙏 |
We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @AccsoSG! 🙏 We will now prioritise the bug and address it appropriately. |
Hey @AccsoSG, I'm honestly unsure whether we ever implemented cardinality checks for union relationships, it's something we need to go away and look at. But this could be a feature request as opposed to a bug in that sense. Thanks, happy holidays! |
Describe the bug
With a To-1 relationship to a union, the library does not check whether only one node is actually connected.
Type definitions
To Reproduce
Steps to reproduce the behavior:
(1) Create movies and episodes
(2) Create PublicationEvent-Object
No filter is specified here for the connection (it has been forgotten). The mutation works anyway. Both movie nodes are connected.
However, only one movie node is returned. It appears undeterministic.
Expected behavior
When executing the second mutation, the following error message should be returned: PublicationEvent.product required exactly once
Screenshots
System (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: