Although inheritance mapping is part of domain objects, we treat it separately due to its importance.
尽管继承映射是领域对象的一部分，出于它的重要性我们将它单独出来。
Chapter 9 "Inheritance Mapping" in HRD [1] already has good coverage, so we will focus on SQL generation and tuning recommendations for each strategy.
hrd[1]中的第9章“继承映射”已经说得很清楚了，所以我们将关注SQL生成和针对每个策略的调优建议。
There are three fundamental solutions for mapping inheritance into a relational database, and to understand them I will discuss the trade-offs of mapping the class diagram presented in Figure 1.
将继承映射到关系数据库中有三种基本解决办法，为更好地理解它们，我将讨论在图1中显示的映射类图表的优缺点。
Mapping rules for fault inheritance.
用于错误继承的映射规则。
The JPA specification defines three types of support for mapping inheritance; only one is mandatory in the current specification
JPA规范定义了对映射继承的三种类型的支持；其中只有一种在当前规范中是强制的
Inheritance is limited: with ActiveRecord, I'm forced to use a mapping strategy called single table inheritance (see Resources), which is not always optimal.
继承也受到限制：使用ActiveRecord时，我被迫使用单表继承映射策略，而该策略并不总是最佳选择。
Walkthrough: Mapping Table-per-Hierarchy Inheritance in Dynamic Data.
逐步解说：在动态资料中对应单表继承。
Walkthrough: Mapping Table-per-Hierarchy Inheritance in Dynamic Data.
逐步解说：在动态资料中对应单表继承。
应用推荐