Skip to content
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

Setting relation fields to nil breaks one-one creation #3100

Closed
AndrewSisley opened this issue Oct 4, 2024 · 0 comments · Fixed by #3101
Closed

Setting relation fields to nil breaks one-one creation #3100

AndrewSisley opened this issue Oct 4, 2024 · 0 comments · Fixed by #3101
Assignees
Labels
area/collections Related to the collections system bug Something isn't working
Milestone

Comments

@AndrewSisley
Copy link
Contributor

AndrewSisley commented Oct 4, 2024

Found by David.

If you set the primary side to nil on multiple objects it prevents linking from the secondary side as it finds multiple objects already linked.

If you set the secondary side to nil on creation it panics.

@AndrewSisley AndrewSisley added bug Something isn't working area/collections Related to the collections system labels Oct 4, 2024
@AndrewSisley AndrewSisley added this to the DefraDB v0.14 milestone Oct 4, 2024
@AndrewSisley AndrewSisley self-assigned this Oct 4, 2024
AndrewSisley added a commit that referenced this issue Oct 4, 2024
## Relevant issue(s)

Resolves #3100

## Description

Treat explicitly set nil values like omitted values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/collections Related to the collections system bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant