#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 akaariai):
It seems clear that not calling get_db_prep_value is a bug. While it might
be backwards incompatible, we don't guarantee backwards incompatibility
for bugs. So, unless it is clear that this is likely to break existing
installations running 1.8, then I think we can go ahead and fix this for
all field types.
It would be interesting to find cases which this change breaks. Can you
show something involving a date field which worked before, but doesn't
work after your patch?
Also, if you have a patch to solve this, please do make a pull request. If
you don't think your PR is actually ready to be merged, you can add [WIP]
to the title of the pull request so that reviewers know this isn't ready
for commit yet.
--
Ticket URL: <https://code.djangoproject.com/ticket/24698#comment:6>
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.7a2eaa14f3d6cb924bb9654d6ae05ccc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
