#27813: BinaryField is inconsistent between sqlite3 and postgresql
-------------------------------------+-------------------------------------
Reporter: Antonio Terceiro | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Antonio Terceiro):
I noticed this because I had a test that checked the value of the
{{{data}}} field after a given operation, and since I was initially
developing against sqlite, I compared the value against a {{{bytes()}}}
literal b{{{'...'}}}. to make the test pass against postgresql as well, I
had to cast the value in the database to {{{bytes()}}} before the
comparison.
I would expect to always get the same type, either {{{bytes}}} or
{{{memoryview}}}. on the other hand, everything else other than that one
test just worked. the view that allows for that data to be downloaded
worked just fine, because {{{bytes}}} and {{{memoryview}}} have a similar
enough interface, so maybe this should be just clearly documented.
--
Ticket URL: <https://code.djangoproject.com/ticket/27813#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.44312ef2b850548363b0b7bf412eabf2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
