Bug: setting reverse OtO is not persisted #7987
Unanswered
pierremonico
asked this question in
Potential Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I have an issue where I have two models
A
andB
.B
has aOneToOne
field calleda
pointing to theA
model, withrelated_name
set tob
.Whenever I create
A
objects through the API and set the JSONb
field to the ID of an existingB
object, I get a201
response (with theb
key correctly set in the response body), but this relationship is actually not persisted in the database .I have created a repo with a minimal implementation where this can be reproduced. It also includes a failing test.
I believe following issues/MRs reference the same problem, but I can't tell for sure:
Beta Was this translation helpful? Give feedback.
All reactions