> Den 19. dec. 2015 kl. 13.15 skrev Cristiano Coelho <cristianocc...@gmail.com>: > > 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.
Can you elaborate on that? You're doing something like: SELECT foo_date FROM my_table WHERE foo_date = '2015-12-24 12:34:56.123456'; and expecting it to return rows where foo_date is '2015-12-24 12:34:56', but it doesn't? I'm not sure that's a bug - it's not the least astonishing to me. Why aren't you stripping microseconds from the datetime values before issuing the query, if your data never has microseconds? 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/9F95A9A1-89C5-4304-AF98-8D76FD09C2DC%40cederstrand.dk. For more options, visit https://groups.google.com/d/optout.
