#24698: Relation clear fails silently when using OneToOneField+UUIDField
-------------------------------------+-------------------------------------
Reporter: webjunkie | Owner: abhaga
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: uuidfield | Triage Stage: Accepted
onetoonefield manytomanyfield |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by abhaga):
Thinking about it, since a `ForeignKey` can refer to any unique field on
the related model, this change is likely to be backward incompatible. The
behavior will change in case of all the fields which implement a
`get_db_prep_value` (ex: DateTimeField). Although it doesn't seem a common
use case to have foreign keys pointing to fields other than `IntegerField`
and `UUIDField`.
The patch is simple but can it be applied in 1.8.x branch?
--
Ticket URL: <https://code.djangoproject.com/ticket/24698#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.cd94904ce7958b17bd4f0d76a842e8f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
