The version of Django you use is going to have a large (code) impact on what is actually happening when calling values_list. The Values[List]QuerySet classes are gone in 1.9. 1.8 implemented a different/better way of converting values from the database to python. from_db_value came about in 1.8 I think which should fast path a lot of conversions. The stackoverflow post you linked to mentions Django 1.7. Can you run exactly the same tests using Django Master/1.9 and report back your findings?
I don't doubt there's room for performance improvements if you go looking. As Anssi said, we'd definitely welcome improvements to performance where they can be found. But you should make sure the kinds of changes you want to make will have an impact when using the latest version of Django, because some of the low hanging fruit may have already been patched. Cheers On Tuesday, 17 November 2015 04:12:11 UTC+11, Cristiano Coelho wrote: > > Interesting, maybe because I'm using MySQL with mysqlclient connector, but > running the straight query with the django cursor wrapper always returns > the correct data types, even dates with its it time zone when time zone is > enabled, was it all coincidence? Would using a different backend break with > a cursor query returning invalid/not expected data? Seems like a lot to test -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8e32b5b0-317e-4c27-9383-dcf00588e056%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
