Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 15 views

    Database Systems: M. Sajid Farooq

    Uploaded by

    M Hassan Munir
    This document summarizes key topics from a lecture on database systems, including: - Relationships can be specified at the supertype or subtype level - Completeness constraints can be total, meaning all supertype instances map to a subtype, or partial - Disjointness constraints require each supertype instance maps to only one subtype, while overlap allows mapping to multiple subtypes - Constraints are independent and can have various combinations like disjoint and total vs. overlapping and partial - An example illustrates disjointness vs. overlap rules using employee subtypes - A practice question involves drawing ERD segments for distributor subtypes under different constraints

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Database Systems: M. Sajid Farooq

    Uploaded by

    M Hassan Munir
    15 views19 pages
    This document summarizes key topics from a lecture on database systems, including: - Relationships can be specified at the supertype or subtype level - Completeness constraints can be total, meaning all supertype instances map to a subtype, or partial - Disjointness constraints require each supertype instance maps to only one subtype, while overlap allows mapping to multiple subtypes - Constraints are independent and can have various combinations like disjoint and total vs. overlapping and partial - An example illustrates disjointness vs. overlap rules using employee subtypes - A practice question involves drawing ERD segments for distributor subtypes under different constraints

    Original Description:

    Inheritance Super type Subtypes Constraints

    Original Title

    Lecture 9

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document summarizes key topics from a lecture on database systems, including: - Relationships can be specified at the supertype or subtype level - Completeness constraints can be total, meaning all supertype instances map to a subtype, or partial - Disjointness constraints require each supertype instance maps to only one subtype, while overlap allows mapping to multiple subtypes - Constraints are independent and can have various combinations like disjoint and total vs. overlapping and partial - An example illustrates disjointness vs. overlap rules using employee subtypes - A practice question involves drawing ERD segments for distributor subtypes under different constraints

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    15 views19 pages

    Database Systems: M. Sajid Farooq

    Uploaded by

    M Hassan Munir
    This document summarizes key topics from a lecture on database systems, including: - Relationships can be specified at the supertype or subtype level - Completeness constraints can be total, meaning all supertype instances map to a subtype, or partial - Disjointness constraints require each supertype instance maps to only one subtype, while overlap allows mapping to multiple subtypes - Constraints are independent and can have various combinations like disjoint and total vs. overlapping and partial - An example illustrates disjointness vs. overlap rules using employee subtypes - A practice question involves drawing ERD segments for distributor subtypes under different constraints

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 19

    DATABASE

    SYSTEMS
    LECTURE 9
    M. SAJID FAROOQ
    Topics to Cover


    Attributes of relationships

    Inheritance

    Super type

    Subtypes

    Constraints

    Completeness

    Disjointness
    Relationships and Subtypes

     Relationships at the supertype level indicate that all


    subtypes will participate in the relationship

     The instances of a subtype may participate in a


    relationship unique to that subtype. In this situation, the
    relationship is shown at the subtype level.
    Relationships and Subtypes
    Specifying Constraints

     Once there has been established a super/sub entity relationship there are a
    number of constraints which can be specified for this relationship for
    specifying further restrictions on the relationship.

     Completeness Constraint
     Total Completeness

     Partial Completeness

     Disjointness Constraint
     Disjointness rule

     Overlap rule
    Completeness Constraint

     There are two types of completeness constraints, partial completeness constraints and
    total completeness constraints.

     Total Completeness: Total Completeness constraint exist only if we have a super


    type and some subtypes associated with that supertype, and the following situation
    exists between the super type and subtype.

     All the instances of the supertype entity must be present in at one of the subtype
    entities, i.e.—there should be not instance of the supertype entity which does not
    belong to any of the subtype entity.
    qualification
    Completeness Constraint

     Total Completeness: This is a specific situation when the supertype


    entities are very carefully analyzed for their associated subtype entities
    and no sub type entity is ignored when deriving sub entities from the
    supertype entity.
    Completeness Constraint

     Partial Constraint: This type of completeness constraint exists when it


    is not necessary for any supertype entity to have its entire instance set to
    be associated with any of the subtype entity.

     This type of situation exists when we do not identify all subtype entities
    associated with a supertype entity, or ignore any subtype entity due to
    less importance of least usage in a specific scenario.
    Disjointness Constraint

     Disjoint constraint: This


    constraint restricts the existence of
    one instance of any supertype
    entity to exactly one instance of
    any of the subtype entities.
    Disjointness Constraint

     Disjoint constraint: From the example, it is seen that there can be two
    types of employees, one which are fixed salary employees and the
    others are hourly paid employees.

     Now the disjoint rule tells that at a certain type an employee will be
    either hourly paid employee or salaried employee, he can not be placed
    in both the categories in parallel.
    Disjointness Constraint

     Overlap Rule: This rule is in contrast with the disjoint rule, and tells that for one
    instance of any supertype entity there can be multiple instances existences of the of the
    instance for more then one subtype entities.

     Again taking the same example of the employee in an organization we can say that one
    employee who is working in an organization can be allowed to work for the company at
    hourly rates also once he has completed his duty as a salaried employee.

     In such a situation the employee instance record for this employee will be stored in
    both the sub entity types.
    Constraints

    Disjointness and Completeness constraints are independent, so you might have


    the following combinations of specializations: –
     Disjoint, total
     Disjoint, partial
     Overlapping, total
     Overlapping, partial
    Practice Question

     The entity type DISTRIBUTOR has three subclasses.


    NORTHERN,SOUTHERN,CENTER, and EASTERN.
     Draw a separate EER diagram segment for each of the following situation.
     a)At a given time, a DISTRIBUTOR must be exactly one of these subclasses.
     b)A DISTRIBUTOR may not be one of these subclass. However, a
    DISTRIBUTOR who is one of those, subclasses can not at the same time be
    one of the other subclasses.
     c)A DISTRIBUTOR may not be of these subclass. On the other hand, a
    DISTRIBUTOR may be any two ( or even three) of these subclasses at the
    same time.
    Part a
    Part b
    Part c
    Next Lecture

     ERD’s using crow foot notation

    You might also like