-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
This is related to #487, which is now closed. #498
Labels
bug
Something isn't working
Comments
amureki
added a commit
that referenced
this issue
Aug 23, 2024
amureki
added a commit
that referenced
this issue
Aug 23, 2024
amureki
added a commit
that referenced
this issue
Aug 23, 2024
Hey Paul! I agree that this should be solved by the library and not by manually updating all the places using GFKs. |
Hi Rust
Once again, many thanks!!
Best,Paul
On Friday, 23 August 2024 at 14:29:31 BST, Rust Saiargaliev ***@***.***> wrote:
Hey Paul!
I agree that this should be solved by the library and not by manually updating all the places using GFKs.
I am adjusting the logic in #499 to handle this behaviour.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
When setting a GenericForeignKey to None, the component parts are created.
To Reproduce
Definition for comms.Message
Expected behavior
If relates_to is set to None, then relates_to_id and relates_to_type_id are both set to None for a GenericForeignKey
Versions
1.19.4
Rust,
I'd appreciate your thoughts on this. We could set relates_to_id and relates_to_type_id explicitly to None in our code, but I'm not sure this is the right answer. Please let me know if you need any more information on this to help diagnose the problem.
The text was updated successfully, but these errors were encountered: