#19954: Storing of Binary fields leads to Exceptions
-------------------------------------+-------------------------------------
Reporter: marcel.ryser.ch@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by marcel.ryser.ch@…):
What about binary values who could be represented as UTF-8 characters but
aren't characters? Then you have a wrong representation of a binary value,
which are not characters, this could lead to confusion.
Django generates the queries (prepared-statements?) by using the field
datatype defined in the model, I guess. Why doesn't the logging starts
there and not when it is all over? There you could easily decide which
mode should be used to represent the value of a field in the log. Binary
fields should really be represented as they are: binary and not converted
to characters, because we don't know (on django side) what kind of binary
data we are dealing with.
--
Ticket URL: <https://code.djangoproject.com/ticket/19954#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
