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

by

First of all, inheritance has not a natural translation to relational database architecture (ok, I know, Oracle Type Objects and some other RDBMS support inheritance but django don’t take advantage of this functionality)

At this point, notice than django generates new tables to subclasses and write lots of left joins to retrieve data from this ‘sub-tables’. And left joins are not your friends. In a high performance scenario, like a game backend or something else, you should avoid it and resolve inheritance ‘by hand’ with some artifacts like nulls, OneToOne or foreign keys. In OneToOne scenario, you can call the related table directly or only if you need it.

… BUT …

“In my opinion (TGW)” you should to include model inheritance in your enterprise projects when it catches to your universe of discourse. I do this, and I save a lot of development hours to my customers thanks to this feature. Also, code becomes clean and elegant and that means easy maintenance (notice that this kind of projects don’t have hundreds or requests by second)

Question by question

Q: What is wrong with this kind of inheritance in Django?
A: Lot of tables, a lot of left joins.

Q: Why are explicit OneToOneFields better?
A: You can access directly to related model without left joins.

Q: Are there any illustrative examples (benchmarks)?
A: No comparable.

Q: Does not select_related() allow us to control when JOINs are invoked?
A: django joins needed tables.

Q: What are the alternatives to multi-table inheritance when I need to reference a base class in another model?
A: Nullification. OneToOne relations and lots of code lines. It depends on application needs.

Q: Are GenericForeignKeys better in this case?
A: Not for me.

Q: What if I need OneToOneField to base model?
A: Write it. There is no problem with this. For example, you can extend User model, and also you can have a OneToOne to User base model for some users.

Conclusion

You should to know the cost of write and maintenance code without model inheritance also the cost of hardware to support model inheritance applications and act accordingly.

Just a joke: you can write it on assembly code, and it will run faster.

Quoting Trey Hunner:

Your time is usually much more expensive than your CPU’s time.

More Related Contents:

  1. Django model instances primary keys do not reset to 1 after all instances are deleted
  2. Hi I am new to Django Framework.getting error :No Module Named
  3. How to upload a file in Django? [closed]
  4. How do I do an OR filter in a Django query?
  5. Django rest framework, use different serializers in the same ModelViewSet
  6. Setting the selected value on a Django forms.ChoiceField
  7. Load a Django template tag library for all views by default
  8. Output Django queryset as JSON
  9. Django directory structure?
  10. What is a context in Django?
  11. Django migrate –fake and –fake-initial explained
  12. How to access array elements in a Django template?
  13. Creating a model and related models with Inline formsets
  14. Execute code in Django after response has been sent to the client
  15. How to handle request.GET with multiple variables for the same parameter in Django
  16. Django m2m form save ” through ” table
  17. Django templates – split string to array
  18. How to get Django and ReactJS to work together?
  19. Django – how to specify a database for a model?
  20. django – ordering queryset by a calculated field
  21. How to reset migrations in Django 1.7
  22. “Post Image data using POSTMAN”
  23. Django model: delete() not triggered
  24. Django 1.8: Create initial migrations for existing schema
  25. Heroku app database resetting
  26. How to reset the sequence for IDs on PostgreSQL tables
  27. django @login_required decorator for a superuser
  28. How to use if/else condition on Django Templates?
  29. Django/DRF – 405 Method not allowed on DELETE operation
  30. django : Serving static files through nginx

Leave a Comment