Doc typos.
parent
2421f10ab5
commit
9a068dde78
|
|
@ -99,7 +99,7 @@ model as the root of a polymorphic inheritance tree::
|
|||
|
||||
from thirdparty import ThirdPartyModel
|
||||
|
||||
class MyThirdPartyBaseModel(PolymorhpicModel, ThirdPartyModel):
|
||||
class MyThirdPartyBaseModel(PolymorphicModel, ThirdPartyModel):
|
||||
pass # or add fields
|
||||
|
||||
Or instead integrating the third party model anywhere into an
|
||||
|
|
@ -181,7 +181,7 @@ Using enhanced Q-objects in any Places
|
|||
--------------------------------------
|
||||
|
||||
The queryset enhancements (e.g. ``instance_of``) only work as arguments
|
||||
to the member functions of a polymorphic queryset. Occationally it may
|
||||
to the member functions of a polymorphic queryset. Occasionally it may
|
||||
be useful to be able to use Q objects with these enhancements in other places.
|
||||
As Django doesn't understand these enhanced Q objects, you need to
|
||||
transform them manually into normal Q objects before you can feed them
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Using vanilla Django, we get the base class objects, which is rarely what we wan
|
|||
Features
|
||||
--------
|
||||
|
||||
* Full admin integation.
|
||||
* Full admin integration.
|
||||
* ORM integration:
|
||||
|
||||
* support for ForeignKey, ManyToManyField, OneToOneField descriptors.
|
||||
|
|
@ -37,7 +37,7 @@ Features
|
|||
* Combining querysets of different models (``qs3 = qs1 | qs2``)
|
||||
* Support for custom user-defined managers.
|
||||
|
||||
* Uses the minumum amount of queries needed to fetch the inherited models.
|
||||
* Uses the minimum amount of queries needed to fetch the inherited models.
|
||||
* Disabling polymorphic behavior when needed.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,3 @@
|
|||
|
||||
|
||||
Custom Managers, Querysets & Manager Inheritance
|
||||
================================================
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue