Erik, I'm using MySQL 5.6.x and indeed it has microseconds support, but that's not the issue.
The issue is that every datetime column created has no microseconds (since they were created with django 1.7, so it is actually a datetime(0) column) and I would like to keep it that way, however, since django 1.8+ will always send microseconds in the query, inserts will go fine (mysql will just ignore them) but SELECTS will all fail since mysql will not strip microseconds from the where clause (even if the column is defined as 0 datetime, duh, really mysql?), so basically everything that uses datetime equaility in the query stopped working. As suggested, all datetime columns should be updated to datetime(6) so it works correctly with the new django behaviour, however, I would like to keep datetime columns as they are, since I don't need microseconds, so I'm wondering if there's any way to get back the old django behaviour for mysql, through a setting, or monkey patch (as long as it works for all models and raw queries). El sábado, 19 de diciembre de 2015, 1:59:00 (UTC-3), Erik Cederstrand escribió: > > > > Den 19. dec. 2015 kl. 07.52 skrev Cristiano Coelho <[email protected] > <javascript:>>: > > > > Hello, > > > > After django 1.8, the mysql backend no longer strips microseconds. > > This is giving me some issues when upgrading from 1.7 (I actually > upgraded to 1.9 directly), since date times are not stored with micro > second precision on mysql, but the queries are sent with them. > > As I see it, my only option is to update all existing date time columns > of all existing tables, which is quite boring since there are many tables. > > Is there a way I can explicitly set the model datetime precision? Will > this work with raw queries also? Could this be a global setting or monkey > patch? This new behaviour basically breaks any '=' query on date times, at > least raw queries (I haven't tested the others) since it sends micro > seconds which are not stripped down. > > MySQL as of version 5.6.4 (and MariaDB) is able to store microseconds in > datetime fields, but you need to set the precision when you create the > column. In Django, this should "just work". Which version of MySQL are you > using, and are your columns created as DATETIME(6)? > > Erik -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2229a467-19d6-4e2f-b510-d49eb6ccf405%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
