mirror of
				https://github.com/django/django.git
				synced 2025-10-31 09:41:08 +00:00 
			
		
		
		
	[5.2.x] Fixed #36335 -- Fixed typo in docs/topics/db/managers.txt.
Backport of 7b394b9988 from main
			
			
This commit is contained in:
		
				
					committed by
					
						 Mariusz Felisiak
						Mariusz Felisiak
					
				
			
			
				
	
			
			
			
						parent
						
							90fa9f4cc0
						
					
				
				
					commit
					c08764cb2e
				
			| @@ -197,7 +197,7 @@ Using managers for related object access | ||||
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||||
|  | ||||
| By default, Django uses an instance of the ``Model._base_manager`` manager | ||||
| class when accessing related objects (i.e. ``choice.question``), not the | ||||
| class when accessing related objects (e.g. ``choice.question``), not the | ||||
| ``_default_manager`` on the related object. This is because Django needs to be | ||||
| able to retrieve the related object, even if it would otherwise be filtered out | ||||
| (and hence be inaccessible) by the default manager. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user