#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
Feels like the issue should be solved at the model level because while it
break `setupTestData` (3cf80d3fcf7446afdde16a2be515c423f720e54d) it also
breaks any form of `QuerySet` or `Model` pickling
{{{#!python
MyModel.objects.create(binary=b'y')
pickle.dumps(MyModel.objects.all())
}}}
This can be reproduced by adding a `BinaryField` to
[https://github.com/django/django/blob/ca9872905559026af82000e46cde6f7dedc897b6/tests/queryset_pickle/models.py#L48
models] in the test `queryset_pickle` apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#comment:3>
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.3630cec4d6b97ea54947bd8dd9cf869c%40djangoproject.com.
