Skip to main content
  • 2263 Accesses

Abstract

We are doing pretty well at designing a database. So far, you have learned how use cases and a data model can help you understand many of the complexities of the actual problem you are trying to represent. In the previous chapter, you saw how to represent the main parts of the data model in a relational database. To recap:

  • Each class is represented by a table

  • Each object becomes a row in a table

  • For each table, we determine a primary key, which is a field(s) that uniquely identifies each row

  • We use the primary key field(s) to represent relationships between tables by way of foreign keys

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Edgar F. Codd, (June 1970). “A Relational Model of Data for Large Shared Data Banks.” Communications of the ACM: 13(6): pp. 377–387.

    Article  MATH  Google Scholar 

Download references

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Clare Churcher

About this chapter

Cite this chapter

(2007). Normalization. In: Beginning Database Design. Apress. https://doi.org/10.1007/978-1-4302-0366-7_8

Download citation

Publish with us

Policies and ethics