Chpt_Supp_2_outline_-_Dbase_design_theory

Chpt_Supp_2_outline_-_Dbase_design_theory - CHAPTER 15...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
CHAPTER 15 – Building and Using the Database Terminology Formal term Common names SQL command entity tuple attribute Cardinalities – See Powerpoint Building a database from an ER diagram (ERD) INVENTORY Resource - SALE Event - CUSTOMER Agent stock flow1 (0,N) (1,N) inside part.1 outside part.1 (0,N) CASH Resource + CASH RECEIPT Event + stock flow2 (0,N) (1,1) outside part.2 inside part.2 duality (0,N) (0,N) (0,N) (0,N) (0,N) EMPLOYEE Agent (1,1) (1,1) (1,1) (0,1)
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Step 1: Create the necessary tables. Each event, resource, and agent gets its own table o Identify the primary key for each table o Determine which other columns should be included in the table Primary keys – Unique identifier for each row in a table See Coding Techniques (pages 34-35) for different methods to assign primary keys. Some other methods:
Background image of page 2
Candidate keys – Entity Integrity Rule Efficiency Constraints – Naming columns Information in columns Entity Integrity Rule Column and row order
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 8

Chpt_Supp_2_outline_-_Dbase_design_theory - CHAPTER 15...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online