List of Figures

Chapter 1. Understanding object/relational persistence

Figure 1.1. A simple UML diagram of the User and BillingDetails entities

Figure 1.2. The User has an Address.

Figure 1.3. Using inheritance for different billing strategies

Chapter 3. Domain models and metadata

Figure 3.1. A persistence layer is the basis in a layered architecture.

Figure 3.2. A class diagram of a typical online auction model

Figure 3.3. Persistent classes of the CaveatEmptor domain model and their relationships

Figure 3.4. Associations between the Item and Bid classes

Chapter 4. Mapping persistent classes

Figure 4.1. Two User instances have a reference to a single Address.

Figure 4.2. Two User instances each have their own dependent Address.

Figure 4.3. Diagramming stereotypes for entities and value types

Chapter 5. Mapping value types

Figure 5.1. Composition of User and Address

Figure 5.2. The columns of the components are embedded in the entity table.

Figure 5.3. Nested composition of Address and City

Figure 5.4. Embedded columns hold Address and City details.

Figure 5.5. The abstract Zipcode class has two concrete subclasses.

Chapter 6. Mapping inheritance

Figure 6.1. Mapping all concrete classes to an independent table

Figure 6.2. Mapping an entire class hierarchy to a single table

Figure 6.3. Mapping all classes of the hierarchy to their own table

Figure 6.4. Breaking out a subclass to its own secondary table

Figure 6.5. Mapping concrete embeddable classes with their inherited properties