#33333: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Adam Zimmerman | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | 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 Simon Charette):
My first instinct would be to have `BinaryField.from_db_value` use
`force_bytes` to store `bytes` instead of `memoryview` in `_state` or
introduce a hook to allow `Field` subclass to define a hook using during
serialization and have the model machinery
To me that's more of a long standing issue with `BinaryField` and less of
a regression cause by 3cf80d3fcf7446afdde16a2be515c423f720e54d.
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.26cbb57ec99d59d46213df34e22e4ca5%40djangoproject.com.
