#17339: [nonrel] Factor out has_result into database backend
-------------------------------------+-------------------------------------
Reporter: jonash | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: nonrel | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by carljm):
Pretty sure the test suite already exercises this code quite heavily, so I
think in this case of a pure refactoring there aren't more tests needed,
as long as the existing ones pass. And obviously docs aren't relevant at
this level either.
In terms of the patch specifics, what's the justification for why some
query modification bits are moved into the compiler's has_results and not
others?
--
Ticket URL: <https://code.djangoproject.com/ticket/17339#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
