How do you deal with polymorphism in a database?

by

Take a look at Martin Fowler’s Patterns of Enterprise Application Architecture:

  • Single Table Inheritance:

    When mapping to a relational database, we try to minimize the joins that can quickly mount up when processing an inheritance structure in multiple tables. Single Table Inheritance maps all fields of all classes of an inheritance structure into a single table.

  • Class Table Inheritance:

    You want database structures that map clearly to the objects and allow links anywhere in the inheritance structure. Class Table Inheritance supports this by using one database table per class in the inheritance structure.

  • Concrete Table Inheritance:

    Thinking of tables from an object instance point of view, a sensible route is to take each object in memory and map it to a single database row. This implies Concrete Table Inheritance, where there’s a table for each concrete class in the inheritance hierarchy.

More Related Contents:

  1. Are nulls in a relational database okay? [closed]
  2. How to design a product table for many kinds of product where each product has many parameters
  3. What is Normalisation (or Normalization)? [closed]
  4. How do you effectively model inheritance in a database?
  5. Database design – articles, blog posts, photos, stories
  6. Schema for a multilanguage database
  7. Calendar Recurring/Repeating Events – Best Storage Method
  8. How to version control a record in a database [closed]
  9. Same data from different entities in Database – Best Practice – Phone numbers example
  10. Sql – Indirect Foreign Key
  11. Defining multiple foreign keys in one table to many tables
  12. What are the lengths of Location Coordinates, latitude and longitude? [closed]
  13. How should I implement this schema in MongoDB?
  14. Why use multiple columns as primary keys (composite primary key)
  15. Database schema which can support specialized properties
  16. Nullable Foreign Key bad practice?
  17. How do I design a database to store properties, selecting attributes by synonyms
  18. Composite primary key or not?
  19. Hash Collision – what are the chances? [closed]
  20. How do you determine how far to normalize a database?
  21. Should I have a dedicated primary key field?
  22. What is the best database schema to support values that are only appropriate to specific rows?
  23. Database design for audit logging [closed]
  24. Should I use a single or multiple database setup for a multi-client application? [closed]
  25. Database Design Best Practices [closed]
  26. A column as primary key or two foreign keys as primary key
  27. How to Store Historical Data [closed]
  28. Bill of materials database model
  29. What are design patterns to support custom fields in an application?
  30. mongodb schema design for blogs

Leave a Comment