#27901: Problem with Django & MySQL & model fields returning custom unicode
classes
-------------------------------------+-------------------------------------
Reporter: Dominique Barton | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: mysql, unicode, | Triage Stage:
error | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
In this case, you need to explain why Django is at fault and ideally
provide a patch that fixes the issue. From what you provided so far, it
looks like you're asking for help debugging your custom field. For ways to
get help with that, see TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/27901#comment:1>
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/068.4d61657efd50d6d5f741d81e33b73d48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
