Improved Django model inheritance with automatic downcasting
Go to file
2026-03-07 07:20:33 -08:00
.github broaden bandit triggers 2026-03-06 21:08:20 -08:00
docs switch default branch master -> main 2026-03-07 07:20:33 -08:00
example [pre-commit.ci] auto fixes from pre-commit.com hooks 2024-03-12 20:23:19 +00:00
src/polymorphic add admin tests for coverage 2026-03-06 21:08:20 -08:00
.gitignore Add bandit security scanning to CI 2026-03-06 11:56:56 -08:00
.pre-commit-config.yaml fix CI on oracle dj5.2 2026-02-09 10:57:59 -08:00
.readthedocs.yaml fix rtd build 2025-08-24 21:37:30 -07:00
AUTHORS.md integrate django-rest-polymorphic 2026-01-13 09:51:16 -08:00
conftest.py A number of changes easing type hint integration: 2026-02-02 15:39:19 -08:00
CONTRIBUTING.md A number of changes easing type hint integration: 2026-02-02 15:39:19 -08:00
justfile Add bandit security scanning to CI 2026-03-06 11:56:56 -08:00
LICENSE updated docs, and moved them to DOCS.rst and README.rst 2010-01-26 14:28:22 +01:00
manage.py add a make-test-migrations recipe that regenerates test migrations using the lowest version of supported django 2025-12-11 15:04:20 -08:00
pyproject.toml switch default branch master -> main 2026-03-07 07:20:33 -08:00
README.md switch default branch master -> main 2026-03-07 07:20:33 -08:00
SECURITY.md Add bandit security scanning to CI 2026-03-06 11:56:56 -08:00
uv.lock Add bandit security scanning to CI 2026-03-06 11:56:56 -08:00

django-polymorphic

License: BSD Ruff PyPI version PyPI pyversions PyPI djversions PyPI status PyPI - Types Documentation Status Code Cov Test Status Lint Status Published on Django Packages OpenSSF Scorecard Jazzband


Postgres MySQL MariaDB SQLite Oracle


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 minimum amount of queries needed to fetch the inherited models.

  • Disabling polymorphic behavior when needed.

Note: 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.

Installation

    $ pip install django-polymorphic
INSTALLED_APPS = [
  ...
  "django.contrib.contenttypes",  # we rely on the contenttypes framework
  "polymorphic"
]

License

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