5 ms·
I think there's an argument for throwing AttributeError instead of silently going to N+1 behaviour.
by lozenge 1mo ago
I think there's an argument for throwing AttributeError instead of silently going to N+1 behaviour.
- JodieBenitez 1mo agoSee sibling comment about fetch modes in coming 6.1 (https://docs.djangoproject.com/en/dev/topics/db/fetch-modes/ https://docs.djangoproject.com/en/dev/topics/db/fetch-modes/), you can have a FieldFetchBlocked.