#24996 closed Bug (wontfix)
Reimplement the DatabaseFeatures.supports_select_related flag
| Reported by: | Tim Graham | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In Django 1.8, the supports_select_related database feature flag was refactored away in 0c7633178fa9410f102e4708cef979b873bccb76. If we add it back, it would be nice to also add a test that mocks the value to False, then checks that a select_related() call doesn't have any effect. The original ticket is #17335.
Note:
See TracTickets
for help on using tickets.
I'm going to close this since no one has complained about it. If some wants to do it, please reopen.