Changes between Version 1 and Version 2 of Ticket #36157
- Timestamp:
- Jan 29, 2025, 4:27:50 PM (25 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36157 – Description
v1 v2 44 44 === Context === 45 45 46 This is an issue that came up in the wild. I'm using a third-party optimiser that improves the performance of graphQL queries by decorating querysets with `only()`, `select_related()` etc. It correctly identifies that I am only using certain fields and applies `only()` to them, knowing I will never need to access certain related fields. This results in django producing many additional hits to the database.46 This is an issue that came up in the wild. I'm using a third-party optimiser that improves the performance of graphQL queries by decorating querysets with `only()`, `select_related()` etc. It correctly identifies that I am only using certain fields and applies `only()` to them, knowing I will never need to access certain related fields. This unfortunately results in django producing many additional hits to the database. I don't think this is expected behaviour from django.