#27901: Problem with Django & MySQL & model fields returning custom unicode
classes
-------------------------------------+-------------------------------------
Reporter: Dominique Barton | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
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 Dominique Barton):
* status: closed => new
* resolution: needsinfo =>
Comment:
Replying to [comment:1 Tim Graham]:
> From what you provided so far, it looks like you're asking for help
debugging your custom field.
No I don't need help with debugging my custom field as my custom field is
not the problem! As I described before, IT IS A BUG and therefore I think
this ticket is quite valid!
Let's keep it simple and ignore the fact that I'm trying to make a custom
model field. Use a stock `TextField`, write a value to it and then save
the model. Now do the same, but use a custom `unicode` class for the
value. Something like that:
https://gist.github.com/domibarton/aa691342321f63f3511bb1ff53b946c7
--
Ticket URL: <https://code.djangoproject.com/ticket/27901#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/068.f5d512cb2d8237cad5b450a1e3752eb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
