#27813: BinaryField type inconsistent between sqlite3 (bytes) and postgresql
(memoryview)
-------------------------------------+-------------------------------------
Reporter: Antonio Terceiro | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Václav Řehák):
The same applies to Oracle backend which also returns bytes. One of the
reasons we use Django in current project is that we can run it on Oracle
(as needed due to historical reasons) but hopefully convert it to
PostgreSQL one day. Subtle differences like this make it more complicated.
What is the reason to return different data type from PostgreSQL backend?
--
Ticket URL: <https://code.djangoproject.com/ticket/27813#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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8cb7b99ada053fd280d407f441aed9bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
