#36815: Avoid unnecessary prepare_value calls when inserting db_defaults
-------------------------------------+-------------------------------------
Reporter: Adam Sołtysik | Owner:
Type: | YashRaj1506
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Sołtysik):
As far as I'm concerned, feel free to submit a PR. I didn't do it myself
mainly because with things like CLA it's a little bit too much bureaucracy
for me. Also, my benchmark was obviously not designed to end up in the
actual test suite. I guess that a proper regression test should be
written, although I'm not sure what's the policy for testing against
executing unnecessary code.
--
Ticket URL: <https://code.djangoproject.com/ticket/36815#comment:12>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b85cb0025-b8733e7c-8bbb-45fa-aace-74f1e2dfa3d5-000000%40eu-central-1.amazonses.com.
