During the final production stages of the book, I decided to add in the section, Mapping Unique Foreign Keys, into Chapter 14. This came with two new figures. Somehow the person who did this task (editing was by this time out of my hands) must have gotten confused and inserted the images in multiple places, creating a bit of chaos in following 20 or so figures in the chapter. The correct images for the last two figures (14-23 and 14-24) disappeared into never never land.
Following are the corrected figure #s and captions. The captions are below the figures. I hope that the publisher will get the correction into the digital version soon. It will not be in print until the next printing.
FIgures 14-1 through 14-6 are correct. In the PDF copy of the book that I have, the problem begins with Figure 14-7. 14-7 and 14-8 are repeats of 14-5 and 14-6.
Figure 14-7. Two database tables that share a primary key and can be represented as a single entity
Figure 14-8. The ContactPersonalInfo entity
Figure 14-9. Mapping an entity to multiple tables
Figure 14-10. The confirmation dialog when deleting entities from the model
Figure 14-11. A screenshot from SQL Profiler showing the commands that are executed when editing a Customer and adding a new Customer
Figure 14-12. Mapping a stored procedure to an entity that is derived from one entity and points to multiple tables
Figure 14-13. Mapping the new entity
Figure 14-14. Defining an association
Figure 14-15. Creating a referential constraint
Figure 14-16. Adding a conditional mapping to the Activity entry indicating that only rows whose Category value is equal to Water should be returned when querying against this entity
Figure 14-17. Changing the condition operator to Is, which turns Value/Property into a drop-down list with the options Not Null and Null
Figure 14-18. The Resort property of the Lodging entity, which suggests a new inherited type, Resort
Figure 14-19. Resort now inheriting from Lodging based on a conditional mapping
Figure 14-20. Creating a complex type from selected properties
Figure 14-21. The renamed complex type in the Model Browser
Figure 14-22. The property that houses the new complex type before it has been renamed
Figure 14-23. Table columns mapped to complex type properties
Figure 14-24. An example of a self-referencing association in the Employee entity, which is created from the Employees table in the Northwind database