Changes between Initial Version and Version 1 of Ticket #35299
- Timestamp:
- Mar 13, 2024, 10:48:42 AM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35299 – Description
initial v1 1 The issue [https://code.djangoproject.com/ticket/34586?utm_campaign=Django%2BNewsletter&utm_medium=web&utm_source=Django_Newsletter_193 #34586] was fixed in [https://github.com/django/django/commit/e02fc588893485e5f5e509cdb67c63d8e1a45b31 commit] by raising an Exception. However, now there is no possibility to create a new row with a OneToOne relation because of the condition {{{if reverse_one_to_one_fields:}}}. I believe that the issue must fix this part {{{create() does not save reverse OneToOne relationship}}}.1 The issue [https://code.djangoproject.com/ticket/34586?utm_campaign=Django%2BNewsletter&utm_medium=web&utm_source=Django_Newsletter_193 #34586] was resolved in [https://github.com/django/django/commit/e02fc588893485e5f5e509cdb67c63d8e1a45b31 commit] by introducing an Exception. However, as a result of the condition {{{if reverse_one_to_one_fields:}}}, it's currently not possible to create a new row with a OneToOne relationship. In my opinion, the issue should address the part {{{create() does not save reverse OneToOne relationship}}} instead of merely adding the Exception.