Slide 1 Advanced Ent it y Relat ionship Concept s Slide 2 Advanced Concept s
- UI Ds
- I nt ersect ion
Ent it ies
- Recur sive
Relat ionships
- Roles
- Subt ypes
- Exclusivit y
- Hist orical
- Fan Traps
- Non t ransf erabilit y
Slide 3 Simple Unique I dent if ier Simple Unique I dent if ier
CUSTOMER # * customer num
Single attribute Tag the UID with #
Slide 4 Compound UI D - At t ribut es Compound UI D - At t ribut es
MEMBERSHIP # * num # * start date
Multiple attributes Members get a new membership each year but keep t heir membership number.
Slide 5
Compound UID - Composite Compound UID - Composite
ACCOUNT * num BANK # * num
What would you need to know to identify a specific instance of ACCOUNT?
Slide 6
Compound UID - Composite Compound UID - Composite
ACCOUNT * num BANK # * num
Use a UID bar to indicate that a relationship is part of the entity’s UID Use # to indicate that the attribute is part of the entity’s UID What would you need to know to identify a specific instance of ACCOUNT?
#
Slide 7
What do you need to know to identify a specific instance of RENTAL ITEM? Rental item requires the rental transaction num and the inventory num
Compound UID - Relationships Compound UID - Relationships
RENTAL ITEM * rental period return date
- RENTAL
# * transaction num * transaction date COPY # * inventory num * purchase cost
Slide 8 Mult i-Level Relat ionship UI Ds Mult i-Level Relat ionship UI Ds
What would you need to know to identify a specific instance of TICKET?
VENUE PLAY # * title PERFORMANCE # * date # * time # * name CUSTOMER # * name TICKET * seat number
Slide 9 Mult i-Level Relat ionship UI Ds Mult i-Level Relat ionship UI Ds
Venue name + Play title + Performance date + Performance time + Customer name
VENUE PLAY # * title PERFORMANCE # * date # * time # * name CUSTOMER # * name TICKET * seat number
Slide 10 Mult iple UI Ds Mult iple UI Ds
badge num payroll num first and last name EMPLOYEE badge num payroll num last name first name
#(1)* #(3) * #(2) * #(2) *