#33333: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Adam Zimmerman | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"cb724ef6c0fd71cd5bdbdc27c02f4da0f7e2ad08" cb724ef6]:
{{{
#!CommitTicketReference repository=""
revision="cb724ef6c0fd71cd5bdbdc27c02f4da0f7e2ad08"
[3.2.x] Fixed #33333 -- Fixed setUpTestData() crash with
models.BinaryField on PostgreSQL.
This makes models.BinaryField pickleable on PostgreSQL.
Regression in 3cf80d3fcf7446afdde16a2be515c423f720e54d.
Thanks Adam Zimmerman for the report.
Backport of 2c7846d992ca512d36a73f518205015c88ed088c from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#comment:13>
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.fe16ce09dabaa7f95e4627a4252b55f8%40djangoproject.com.
