#26140: BinaryField value must be declared "binary" in queries to avoid MySQL
5.7+
warning
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"204e00c0c57c34528157a739389b6935e4af2f36" 204e00c0]:
{{{
#!CommitTicketReference repository=""
revision="204e00c0c57c34528157a739389b6935e4af2f36"
Fixed #26140 -- Suppressed MySQL warning when inserting binary content
Thanks Tim Graham for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26140#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ef7c9b1dee31019e437838bc3d5dca0b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
