[3.0.x] Fixed #27865 -- Adjusted docs example to avoid confusion with models.BaseManager.
Backport of a2f554249ec07d4643643773a995579f98564ac1 from master
This commit is contained in:
parent
0fde2664f6
commit
0f524f5686
@ -330,7 +330,7 @@ For advanced usage you might want both a custom ``Manager`` and a custom
|
||||
returns a *subclass* of your base ``Manager`` with a copy of the custom
|
||||
``QuerySet`` methods::
|
||||
|
||||
class BaseManager(models.Manager):
|
||||
class CustomManager(models.Manager):
|
||||
def manager_only_method(self):
|
||||
return
|
||||
|
||||
@ -339,14 +339,14 @@ returns a *subclass* of your base ``Manager`` with a copy of the custom
|
||||
return
|
||||
|
||||
class MyModel(models.Model):
|
||||
objects = BaseManager.from_queryset(CustomQuerySet)()
|
||||
objects = CustomManager.from_queryset(CustomQuerySet)()
|
||||
|
||||
You may also store the generated class into a variable::
|
||||
|
||||
CustomManager = BaseManager.from_queryset(CustomQuerySet)
|
||||
MyManager = CustomManager.from_queryset(CustomQuerySet)
|
||||
|
||||
class MyModel(models.Model):
|
||||
objects = CustomManager()
|
||||
objects = MyManager()
|
||||
|
||||
.. _custom-managers-and-inheritance:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user