I think a simple setting allowing to use the old behaviour should be enough, shouldn't it? How does it handle other db backends? I'm not sure if oracle has an option for datetime precision, but if it does, it makes sense to have a global setting for datetime precision, as right now you are pretty much forced to always go with a precision of 6 (at least on mysql?) and that might be just too much if you want a simpler datetime.
El lunes, 21 de diciembre de 2015, 19:54:29 (UTC-3), Josh Smeaton escribió: > > I think this is a fairly big oversight that should be fixed in the most > backwards compatible way, so users don't need to change their code, or only > have to change it minimally. I'm with Aymeric here. Does Django have > visibility of the field constraints at insert/select queryset time? Ideally > Django would handle the differences transparently. If that's not possible > then we should have a migration or script that'll do the conversion on > behalf of users once off. > > ./manage.py mysql-upgrade-microseconds && ./manage.py migrate ? > > > On Monday, 21 December 2015 19:39:44 UTC+11, Aymeric Augustin wrote: >> >> 2015-12-20 22:57 GMT+01:00 Cristiano Coelho <cristia...@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/78eb038d-a11f-47ec-bf85-ef454341af01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
