#30191: UnicodeDecodeError from non-FK field when using .delete() after Python 3
upgrade
-------------------------------------+-------------------------------------
Reporter: Ed Morley | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: mysql | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ed Morley):
Hi! Thank you for the reply and examples.
However it seems like this should be the default behaviour for
`.delete()`?
If so, can we use this ticket to track that?
Also in the issue we were seeing, the additional fields being selected
were from a model different to the one on which the `.delete()` was being
called, so I don't think the `.only()` would help? (Or at least the docs
don't show a way to apply `.only()` to a nested relation;
https://docs.djangoproject.com/en/1.11/ref/models/querysets/#django.db.models.query.QuerySet.only
?)
--
Ticket URL: <https://code.djangoproject.com/ticket/30191#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a1d57b0d632949b33138bb3e6695a367%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
