Go to file
Jonas Haag 0b87a5ecc8 Fixed a Python >= 3.7 incompatibility (see PEP 479) 2015-12-16 10:31:36 -03:00
docs Update documentation to reflect recent changes 2015-10-21 22:16:35 -03:00
example Add an example that reproduces a pending issue 2015-12-16 10:31:36 -03:00
polymorphic Fixed a Python >= 3.7 incompatibility (see PEP 479) 2015-12-16 10:31:36 -03:00
.gitignore Add wheel support 2014-10-14 16:30:18 +02:00
.travis.yml Fix .travis.yml syntax 2015-09-29 10:07:08 +02:00
AUTHORS.rst update AUTHORS 2014-09-22 16:01:07 +02:00
LICENSE updated docs, and moved them to DOCS.rst and README.rst 2010-01-26 14:28:22 +01:00
MANIFEST.in Include templates in install. 2012-12-10 18:02:12 +01:00
README.rst Updated README.rst 2014-09-28 15:10:16 -04:00
runtests.py Make runtests compatible with older django versions again 2015-12-16 10:31:36 -03:00
setup.cfg Add wheel support 2014-10-14 16:30:18 +02:00
setup.py setup.py: add Django trove classifiers 2015-04-10 12:30:47 +02:00
tox.ini Run tests on py35 as well 2015-12-16 10:31:36 -03:00

README.rst

.. image::  https://travis-ci.org/chrisglass/django_polymorphic.png?branch=master
  :target: http://travis-ci.org/chrisglass/django_polymorphic
  :alt: build-status

Polymorphic Models for Django
=============================

Django-polymorphic simplifies using inherited models in Django projects.
When a query is made at the base model, the inherited model classes are returned.

When we store models that inherit from a ``Project`` model...

>>> Project.objects.create(topic="Department Party")
>>> ArtProject.objects.create(topic="Painting with Tim", artist="T. Turner")
>>> ResearchProject.objects.create(topic="Swallow Aerodynamics", supervisor="Dr. Winter")

...and want to retrieve all our projects, the subclassed models are returned!

>>> Project.objects.all()
    [ <Project:         id 1, topic "Department Party">,
      <ArtProject:      id 2, topic "Painting with Tim", artist "T. Turner">,
      <ResearchProject: id 3, topic "Swallow Aerodynamics", supervisor "Dr. Winter"> ]

Using vanilla Django, we get the base class objects, which is rarely what we wanted:

>>> Project.objects.all()
    [ <Project: id 1, topic "Department Party">,
      <Project: id 2, topic "Painting with Tim">,
      <Project: id 3, topic "Swallow Aerodynamics"> ]

This also works when the polymorphic model is accessed via
ForeignKeys, ManyToManyFields or OneToOneFields.

Features
--------

* Full admin integration.
* ORM integration:

 * support for ForeignKey, ManyToManyField, OneToOneField descriptors.
 * Filtering/ordering of inherited models (``ArtProject___artist``).
 * Filtering model types: ``instance_of(...)`` and ``not_instance_of(...)``
 * 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.
* Disabling polymorphic behavior when needed.

While *django-polymorphic* makes subclassed models easy to use in Django,
we still encourage to use them with caution. Each subclassed model will require
Django to perform an ``INNER JOIN`` to fetch the model fields from the database.
While taking this in mind, there are valid reasons for using subclassed models.
That's what this library is designed for!

For more information, see the `documentation at Read the Docs <https://django-polymorphic.readthedocs.org/>`_.

License
=======

Django-polymorphic uses the same license as Django (BSD-like).