&lt;!-- language-all: lang-python --&gt;

Many experienced developers recommend against using [Django multi-table inheritance][mti] because of its poor performance:

1. [Django gotcha: concrete inheritance][gotcha] by [Jacob Kaplan-Moss][moss], a core contributor of Django.

  &gt; In nearly every case, abstract inheritance is a better approach for
  &gt; the long term. I’ve seen more than few sites crushed under the load
  &gt; introduced by concrete inheritance, so I’d strongly suggest that
  &gt; Django users approach any use of concrete inheritance with a large
  &gt; dose of skepticism.

2. [Two Scoops of Django][scoops] by [Daniel Greenfield][pydanny] ([@pydanny])

  &gt; Multi-table inheritance, sometimes called “concrete inheritance,” is
  &gt; considered by the authors and many other developers to be a bad thing.
  &gt; We strongly recommend against using it.

  &gt; At all costs, everyone should avoid multi-table inheritance
  &gt; since it adds both confusion and substantial overhead.
  &gt; Instead of multi-table inheritance, use explicit OneToOneFields and
  &gt; ForeignKeys between models so you can control when joins are
  &gt; traversed.

But without multi-table inheritance, I can&#39;t easily

1. [Reference base model in another model][1] (have to use GenericForeignKey or reverse dependency);

2. [Get all instances of base model][2].

   *(feel free to add more)*


So what is wrong with this kind of inheritance in Django? Why are explicit OneToOneFields better?

How much does performance suffer from JOINs? Are there any benchmarks that show the difference in performance?

&lt;s&gt;Does not `select_related()` allow us to control when JOINs are invoked?&lt;/s&gt;


----

I have moved concrete examples to a [separate question][1] since this one is becoming too broad, and added a list of reasons for using multi-table inheritance instead.


[mti]: https://docs.djangoproject.com/en/1.5/topics/db/models/#multi-table-inheritance
[scoops]: http://www.amazon.com/Two-Scoops-Django-Best-Practices/dp/1481879707
[pydanny]: http://pydanny.com/
[@pydanny]: https://stackoverflow.com/users/93270/pydanny
[gotcha]: http://jacobian.org/writing/concrete-inheritance/
[moss]: http://jacobian.org/

[1]: https://stackoverflow.com/questions/23555478/django-onetoonefield-to-multiple-models
[2]: https://stackoverflow.com/questions/1729784/django-get-all-implementations-of-an-abstract-base-class

All Concrete Inheritance Solutions on Gang of Coders

Total of 1 Concrete Inheritance Solutions

Should I avoid multi-table (concrete) inheritance in Django by any means?