Ticket #19716: 19716-1.diff

django/db/backends/mysql/base.py

@@ -371 +371 @@
             else:
                 raise ValueError("MySQL backend does not support timezone-aware datetimes when USE_TZ is False.")
 
-        # MySQL doesn't support microseconds
-        return six.text_type(value.replace(microsecond=0))
+        return six.text_type(value)
 
     def value_to_db_time(self, value):
         if value is None:
@@ -382 +381 @@
         if timezone.is_aware(value):
             raise ValueError("MySQL backend does not support timezone-aware times.")
 
-        # MySQL doesn't support microseconds
-        return six.text_type(value.replace(microsecond=0))
-
-    def year_lookup_bounds_for_datetime_field(self, value):
-        # Again, no microseconds
-        first, second = super(DatabaseOperations, self).year_lookup_bounds_for_datetime_field(value)
-        return [first.replace(microsecond=0), second.replace(microsecond=0)]
+        return six.text_type(value)
 
     def max_name_length(self):
         return 64

docs/releases/1.8.txt

@@ -88 +88 @@
 
 * ...
 
+Database backends
+^^^^^^^^^^^^^^^^^
+
+* When Django saves ``datetime`` values through the MySQL backend, it does no
+  longer strip microseconds, letting the database decide if it will discard
+  them or not (MySQL 5.6.4 and up supports fractional seconds depending on the
+  declaration of the datetime field).
+
 Email
 ^^^^^