Scribd Logo
Upload

Welcome to Scribd!

  • 52 views

    Chapter 6: Integrity Constraints: Domain Constraints Referential Integrity Assertions Triggers Functional Dependencies

    Uploaded by

    Yogeswari
    This document discusses different types of integrity constraints in databases including domain constraints, referential integrity, assertions, triggers, and functional dependencies. Domain constraints restrict the values that can be inserted into attributes while referential integrity ensures relationships between relations are maintained. Assertions allow predicates to check conditions in the database and triggers automatically execute actions in response to data modifications.

    Copyright:

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

    Chapter 6: Integrity Constraints: Domain Constraints Referential Integrity Assertions Triggers Functional Dependencies

    Uploaded by

    Yogeswari
    52 views18 pages
    This document discusses different types of integrity constraints in databases including domain constraints, referential integrity, assertions, triggers, and functional dependencies. Domain constraints restrict the values that can be inserted into attributes while referential integrity ensures relationships between relations are maintained. Assertions allow predicates to check conditions in the database and triggers automatically execute actions in response to data modifications.

    Original Description:

    sql language

    Original Title

    sql

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses different types of integrity constraints in databases including domain constraints, referential integrity, assertions, triggers, and functional dependencies. Domain constraints restrict the values that can be inserted into attributes while referential integrity ensures relationships between relations are maintained. Assertions allow predicates to check conditions in the database and triggers automatically execute actions in response to data modifications.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    52 views18 pages

    Chapter 6: Integrity Constraints: Domain Constraints Referential Integrity Assertions Triggers Functional Dependencies

    Uploaded by

    Yogeswari
    This document discusses different types of integrity constraints in databases including domain constraints, referential integrity, assertions, triggers, and functional dependencies. Domain constraints restrict the values that can be inserted into attributes while referential integrity ensures relationships between relations are maintained. Assertions allow predicates to check conditions in the database and triggers automatically execute actions in response to data modifications.

    Copyright:

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

    '

    Chapter 6: Integrity Constraints

    Domain Constraints
    Referential Integrity
    Assertions
    Triggers
    Functional Dependencies

    &

    Database Systems Concepts

    6.1

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Domain Constraints

    Integrity constraints guard against accidental damage to the


    database, by ensuring that authorized changes to the
    database do not result in a loss of data consistency.
    Domain constraints are the most elementary form of integrity
    constraint.
    They test values inserted in the database, and test queries to
    ensure that the comparisons make sense.

    &

    Database Systems Concepts

    6.2

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Domain Constraints (Cont.)

    The check clause in SQL-92 permits domains to be restricted:


    Use check clause to ensure that an hourly-wage domain
    allows only values greater than a specified value.
    create domain hourly-wage numeric(5,2)
    constraint value-test check(value >= 4.00)
    The domain hourly-wage is declared to be a decimal
    number with 5 digits, 2 of which are after the decimal point
    The domain has a constraint that ensures that the
    hourly-wage is greater than 4.00.

    &

    The clause constraint value-test is optional; useful to


    indicate which constraint an update violated.

    Database Systems Concepts

    6.3

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Referential Integrity

    Ensures that a value that appears in one relation for a given


    set of attributes also appears for a certain set of attributes in
    another relation.
    Example: if Perryridge is a branch name appearing in one
    of the tuples in the account relation, then there exists a
    tuple in the branch relation for branch Perryridge.
    Formal Definition
    Let r1 (R1 ) and r2 (R2 ) be relations with primary keys K1 and
    K2 respectively.

    &

    The subset of R2 is a foreign key referencing K1 in


    relation r1 , if for every t2 in r2 there must be a tuple t1 in r1
    such that t1 [K1 ] = t2 [].

    Referential integrity constraint: (r2 ) K1 (r1 )

    Database Systems Concepts

    6.4

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Referential Integrity in the E-R Model

    Consider relationship set R between entity sets E1 and E2 .


    The relational schema for R includes the primary keys K1 of E1
    and K2 of E2 .
    Then K1 and K2 form foreign keys on the relational schemas
    for E1 and E2 respectively.
    Weak entity sets are also a source of referential integrity
    constraints. For, the relation schema for a weak entity set must
    include the primary key of the entity set on which it depends.

    &

    Database Systems Concepts

    6.5

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Database Modification

    The following tests must be made in order to preserve the


    following referential integrity constraint:
    (r2 ) K (r1 )
    Insert. If a tuple t2 is inserted into r2 , the system must ensure
    that there is a tuple t1 in r1 such that t1 [K ] = t2 []. That is

    t2 [] K (r1 )
    Delete. If a tuple t1 is deleted from r1 , the system must
    compute the set of tuples in r2 that reference t1 :

    &

    = t1 [K ] (r2 )

    If this set is not empty, either the delete command is rejected


    as an error, or the tuples that reference t1 must themselves be
    deleted (cascading deletions are possible).

    Database Systems Concepts

    6.6

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Database Modification (Cont.)

    Update. There are two cases:


    If a tuple t2 is updated in relation r2 and the update modifies
    values for the foreign key , then a test similar to the insert
    case is made. Let t2 0 denote the new value of tuple t2 . The
    system must ensure that
    t2 0 [] K (r1 )
    If a tuple t1 is updated in r1 , and the update modifies values
    for the primary key (K ), then a test similar to the delete
    case is made. The system must compute
    = t1 [K ] (r2 )

    &

    using the old value of t1 (the value before the update is


    applied). If this set is not empty, the update may be rejected
    as an error, or the update may be cascaded to the tuples in
    the set, or the tuples in the set may be deleted.

    Database Systems Concepts

    6.7

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Referential Integrity in SQL

    Primary and candidate keys and foreign keys can be specified


    as part of the SQL create table statement:
    The primary key clause of the create table statement
    includes a list of the attributes that comprise the primary
    key.
    The unique key clause of the create table statement
    includes a list of the attributes that comprise a candidate
    key.

    &

    The foreign key clause of the create table statement


    includes both a list of the attributes that comprise the
    foreign key and the name of the relation referenced by the
    foreign key.

    Database Systems Concepts

    6.8

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Referential Integrity in SQL - Example

    create table customer


    (customer-name char(20) not null,
    customer-street char(30),
    customer-city
    char(30),
    primary key (customer-name))

    &

    Database Systems Concepts

    create table branch


    (branch-name
    char(15) not null,
    branch-city
    char(30),
    assets
    integer,
    primary key (branch-name))

    6.9

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Referential Integrity in SQL - Example (Cont.)

    create table account


    (branch-name
    char(15),
    account-number char(10) not null,
    balance
    integer,
    primary key (account-number),
    foreign key (branch-name) references branch)
    create table depositor
    (customer-name char(20) not null,
    account-number char(10) not null,
    primary key (customer-name, account-number),
    foreign key (account-number) references account,
    foreign key (customer-name) references customer )

    &

    Database Systems Concepts

    6.10

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Cascading Actions in SQL

    create table account


    ...
    foreign key (branch-name) references branch
    on delete cascade
    on update cascade,
    ... )
    Due to the on delete cascade clauses, if a delete of a tuple in
    branch results in referential-integrity constraint violation, the
    delete cascades to the account relation, deleting the tuple
    that refers to the branch that was deleted.

    &

    Cascading updates are similar.

    Database Systems Concepts

    6.11

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Cascading Actions in SQL (Cont.)

    If there is a chain of foreign-key dependencies across multiple


    relations, with on delete cascade specified for each
    dependency, a deletion or update at one end of the chain can
    propagate across the entire chain.
    If a cascading update or delete causes a constraint violation
    that cannot be handled by a further cascading operation, the
    system aborts the transaction. As a result, all the changes
    caused by the transaction and its cascading actions are
    undone.

    &

    Database Systems Concepts

    6.12

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Assertions

    An assertion is a predicate expressing a condition that we wish


    the database always to satisfy.
    An assertion in SQL-92 takes the form
    create assertion <assertion-name> check <predicate>
    When an assertion is made, the system tests it for validity. This
    testing may introduce a significant amount of overhead; hence
    assertions should be used with great care.

    &

    Database Systems Concepts

    6.13

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Assertion Example

    The sum of all loan amounts for each branch must be less than
    the sum of all account balances at the branch.
    create assertion sum-constraint check
    (not exists (select * from branch
    where (select sum(amount ) from loan
    where loan.branch-name = branch.branch-name)
    >= (select sum(amount ) from account
    where loan.branch-name = branch.branch-name)))

    &

    Database Systems Concepts

    6.14

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Assertion Example

    Every loan has at least one borrower who maintains an


    account with a minimum balance of $1000.00.
    create assertion balance-constraint check
    (not exists (select * from loan
    where not exists ( select *
    from borrower , depositor , account
    where loan.loan-number = borrower.loan-number
    and borrower.customer-name = depositor.customer-name
    and depositor.account-number = account.account-number
    and account.balance >= 1000)))

    &

    Database Systems Concepts

    6.15

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Triggers

    A trigger is a statement that is executed automatically by the


    system as a side effect of a modification to the database.
    To design a trigger mechanism, we must:
    Specify the conditions under which the trigger is to be
    executed.
    Specify the actions to be taken when the trigger executes.
    The SQL-92 standard does not include triggers, but many
    implementations support triggers.

    &

    Database Systems Concepts

    6.16

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Trigger Example

    Suppose that instead of allowing negative account balances,


    the bank deals with overdrafts by
    setting the account balance to zero
    creating a loan in the amount of the overdraft
    giving this loan a loan number identical to the account
    number of the overdrawn account
    The condition for executing the trigger is an update to the
    account relation that results in a negative balance value.

    &

    Database Systems Concepts

    6.17

    c
    Silberschatz, Korth and Sudarshan 1997

    '

    Trigger Example (Cont.)

    define trigger overdraft on update of account T


    (if new T.balance < 0
    then (insert into loan values
    (T.branch-name, T.account-number , new T.balance)
    insert into borrower
    (select customer-name, account-number
    from depositor
    where T.account-number = depositor.account-number )
    update account S
    set S.balance = 0
    where S.account-number = T.account-number ))

    &

    The keyword new used before T.balance indicates that the value of
    T.balance after the update should be used; if it is omitted, the value
    before the update is used.

    Database Systems Concepts

    6.18

    c
    Silberschatz, Korth and Sudarshan 1997

    You might also like