Skip to content
Browse files

Reverted [8318] and [8329], since the change turned out to have no ef…

…fect, upon

closer examination of the C-library layer.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 4881a4f commit 93462f95167db14e17df2abeafc1abb1203f34ac @malcolmt malcolmt committed
Showing with 0 additions and 12 deletions.
  1. +0 −12 django/db/backends/mysql/
12 django/db/backends/mysql/
@@ -51,18 +51,6 @@
FIELD_TYPE.DECIMAL: util.typecast_decimal,
FIELD_TYPE.NEWDECIMAL: util.typecast_decimal,
-if hasattr(FIELD_TYPE, "VARCHAR"):
- # By default, MySQLdb will return VARCHAR BINARY fields as type str.
- # This is a bad idea, as BINARY doesn't indicate that it's arbitrary
- # binary data, but that collation uses the binary representation.
- # Replacing the list makes it return unicode. MySQLdb later adds
- # another list entry for non-binary fields.
- #
- # MySQLdb 1.2.1p2 doesn't have the VARCHAR attribute, but it also returns
- # unicode for VARCHAR BINARY columns automatically, so we don't need it
- # there.
- django_conversions[FIELD_TYPE.VARCHAR] = [(FLAG.BINARY,
- lambda s: s.decode('utf-8'))]
# This should match the numerical portion of the version numbers (we can treat
# versions like 5.0.24 and 5.0.24a as the same). Based on the list of version

0 comments on commit 93462f9

Please sign in to comment.
Something went wrong with that request. Please try again.