#18757: Examine ways to get rid of DB backend convert_values()
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: mjtamlyn
Type: | Status: assigned
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by mjtamlyn):
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
Comment:
POC at https://github.com/django/django/pull/3047
I agree with your comments akaariai - will try to update to use that
approach. Most of the code is currently in removing `convert_values`
rather than in the details of what happens afterwards. If I get the POC
all green, the performance *should* be easier.
For my own notes, I believe #21565 should get fixed by this as well, and
so I should write a failing test for it. At least if I can get a working
spatialite setup anyway...
--
Ticket URL: <https://code.djangoproject.com/ticket/18757#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1bfa4361d0aa1e338ea6ba5e215ad171%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
