2015-12-20 22:57 GMT+01:00 Cristiano Coelho <cristianocc...@gmail.com>:
> Thanks for the suggestion, I think that work around might just add too > much code, so I'm probably going the way of converting every datetime > column of every table to datetime(6) and afford the extra storage (and > probably a little performance impact ?). > I think the documented change might need a little more of attention, and > mention something about that any equality query will stop working if you > either don't strip microseconds or update datetime columns to datetime(6) > (and not even datetime(3) will work...) > If that's the solution we end up recommending -- because the horse has left the barn months ago... -- then we must document it in detail. This is a large backwards incompatibility that may result in subtle bugs and requires non-trivial steps to fix. It doesn't live up to Django's standards. -- Aymeric. -- 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/CANE-7mUbPJVxwspfK4i1J85rJfxNXMxFTjyYDWs69e6LEG21MA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
