109
Module 3: Relational Model G.Anuradha

Module 3: Relational Model

Embed Size (px)

DESCRIPTION

Module 3: Relational Model. G.Anuradha. Module 3: Relational Model. Concept of a Relation keys Structure relation database Relational algebra and extended algebra options Formation of queries Modification of the Database views. Example of a Relation. Basic Structure. - PowerPoint PPT Presentation

Citation preview

Page 1: Module 3: Relational Model

Module 3: Relational Model

G.Anuradha

Page 2: Module 3: Relational Model

Module 3: Relational Model

• Concept of a Relation• keys• Structure relation database• Relational algebra and extended algebra options• Formation of queries• Modification of the Database• views

Page 3: Module 3: Relational Model

Example of a Relation

Page 4: Module 3: Relational Model

Basic Structure• Formally, given sets D1, D2, …. Dn a relation r is a subset of

D1 x D2 x … x Dn

Thus, a relation is a set of n-tuples (a1, a2, …, an) where each ai Di

• Example: If

– customer_name = {Jones, Smith, Curry, Lindsay, …} /* Set of all customer names */

– customer_street = {Main, North, Park, …} /* set of all street names*/

– customer_city = {Harrison, Rye, Pittsfield, …} /* set of all city names */

Then r = { (Jones, Main, Harrison), (Smith, North, Rye), (Curry, North, Rye), (Lindsay, Park, Pittsfield) } is a relation over

customer_name x customer_street x customer_city

Page 5: Module 3: Relational Model

Attribute Types• Each attribute of a relation has a name• The set of allowed values for each attribute is called the domain of the

attribute• Attribute values are (normally) required to be atomic; that is, indivisible

– E.g. the value of an attribute can be an account number, but cannot be a set of account numbers

• Domain is said to be atomic if all its members are atomic• The special value null is a member of every domain• The null value causes complications in the definition of many operations

– We shall ignore the effect of null values in our main presentation and consider their effect later

Page 6: Module 3: Relational Model

Relation Schema• A1, A2, …, An are attributes

• R = (A1, A2, …, An ) is a relation schema

Example:- (Account_schema denotes the relation schema for account)

Account_schema = (account_number, branch_name,balance)

account is the relation on Account Schema account(Account_schema)

r(R) denotes a relation r on the relation schema R • Relation Schema consists of a list of attributes and their corresponding

domains.• Relation Instance corresponds to the value of a variable.

Page 7: Module 3: Relational Model

Relation Instance• The current values (relation instance) of a relation are specified by a table• An element t of r is a tuple, represented by a row in a table Branch-schema= (branch_name,branch_city, assets)

BrightonDowntownMianusNorth TownPerryridge

Branch_name

BrooklynBrooklynHorseneckRyeHoreseneck

Branch_city

7100000900000040000037000001700000

assets

customer

attributes(or columns)

tuples(or rows)

Page 8: Module 3: Relational Model

Relations are Unordered

Order of tuples is irrelevant (tuples may be stored in an arbitrary order) Example: account relation with unordered tuples

Page 9: Module 3: Relational Model

Database• A database consists of multiple relations

• Information about an enterprise is broken up into parts, with each relation storing one part of the information

account : stores information about accounts depositor : stores information about which customer owns which account customer : stores information about customers

• Storing all information as a single relation such as bank(account_number, balance, customer_name, ..)results in

– repetition of information

• e.g.,if two customers own an account

– the need for null values

• e.g., to represent a customer without an account

• Normalization theory deals with how to design relational schemas

Page 10: Module 3: Relational Model

The customer Relation

Page 11: Module 3: Relational Model

The depositor Relation

Page 12: Module 3: Relational Model

account

customer loan

branch

Account_number balance

Account-branch

Branch-nameassets

Branch_city

depositor

Customer-name Customer-city

customer-street

borrower

Loan-number amount

loan-branch

Page 13: Module 3: Relational Model

Keys• Let K R• K is a superkey of R if values for K are sufficient to identify a unique tuple of each

possible relation r(R) – by “possible r ” we mean a relation r that could exist in the enterprise we are

modeling.

– Example: In Branch-schema, {branch-name} & {branch-name, branch-city} are

both super keys

Page 14: Module 3: Relational Model

Keys (Cont.)• K is a candidate key if K is minimal

{branch-name, branch-city} is not a candidate key because {branch-name} is a subset of {branch-name, branch-city} and {branch-name} is itself a superkey.

• Primary key: a candidate key chosen as the principal means of identifying tuples within a relation

– Should choose an attribute whose value never, or very rarely, changes.

– {branch-name} also serves as a primary key

Page 15: Module 3: Relational Model

Foreign Keys• A relation schema may have an attribute that

corresponds to the primary key of another relation. The attribute is called a foreign key.– E.g. customer_name and account_number

attributes of depositor are foreign keys to customer and account respectively.

– Only values occurring in the primary key attribute of the referenced relation may occur in the foreign key attribute of the referencing relation.

Page 16: Module 3: Relational Model

Schema diagram

Page 17: Module 3: Relational Model

Query Languages• Language in which user requests information from the database.• Categories of languages

– Procedural – PL/SQL– Non-procedural, or declarative -SQL

• “Pure” languages:– Relational algebra (procedural)– Tuple relational calculus (nonprocedural)– Domain relational calculus(nonprocedural)Pure languages form underlying basis of query languages that people use.

Page 18: Module 3: Relational Model

Relational Algebra• Procedural language• Six basic operators

– select: -unary operator– project: -unary operator– union: -binary operator– set difference: – binary operator– Cartesian product: x – binary operator– rename: - unary operator

• The operators take one or two relations as inputs and produce a new relation as a result.

Page 19: Module 3: Relational Model

Select Operation• Notation: p(r)• p is called the selection predicate• Defined as:

p(r) = {t | t r and p(t)}

Where p is a formula in propositional calculus consisting of terms connected by : (and), (or), (not)

• Example of selection:

branch_name=“Perryridge”(account) branch_name=“Perryridge”^ amount >1200 (account) Write a query to find all employees earning more than 1000Write a query to find all employees earning more than 2000

and working as a CLERK

Page 20: Module 3: Relational Model

Select Operation – ExampleRelation r

A B C D

1

5

12

23

7

7

3

10

A=B ^ D > 5 (r)A B C D

1

23

7

10

Page 21: Module 3: Relational Model

Project Operation• Notation:

where A1, A2 are attribute names and r is a relation name.

• The result is defined as the relation of k columns obtained by erasing the columns that are not listed

• Duplicate rows removed from result, since relations are sets• Example: To eliminate the branch_name attribute of account

account_number, balance (account)

Write a query to display only the empno and empnames from emp table

)( ,,, 21r

kAAA

Page 22: Module 3: Relational Model

Project Operation – Example• Relation r: A B C

10

20

30

40

1

1

1

2

A C

1

1

1

2

=

A C

1

1

2

A,C (r)

Page 23: Module 3: Relational Model

Composition of Operations

customer_name ( customer_city = “Harrison” (customer))

Select customer_name from customer where customer_city=“Harrison”

Page 24: Module 3: Relational Model

Banking Example

branch (branch_name, branch_city, assets)

customer (customer_name, customer_street, customer_city)

account (account_number, branch_name, balance)

loan (loan_number, branch_name, amount)

depositor (customer_name, account_number)

borrower (customer_name, loan_number)

Page 25: Module 3: Relational Model

Union Operation• Notation: r s• Defined as:

r s = {t | t r or t s}• For r s to be valid.

1. r, s must have the same arity (same number of attributes)2. The attribute domains must be compatible (example: 2nd column of r deals with the same type of values as does the 2nd

column of s)

• Example: to find all customers with either an account or a loan

customer_name (depositor) customer_name (borrower)

Page 26: Module 3: Relational Model

Union Operation – Example• Relations r, s:

r s:

A B

1

2

1

A B

2

3

rs

A B

1

2

1

3

Page 27: Module 3: Relational Model

Set Difference Operation• Notation r – s• Defined as:

r – s = {t | t r and t s}

• Set differences must be taken between compatible relations.– r and s must have the same arity– attribute domains of r and s must be compatible

customer_name (depositor) - customer_name (borrower)

Page 28: Module 3: Relational Model

Set Difference Operation – Example• Relations r, s:

r – s:

A B

1

2

1

A B

2

3

rs

A B

1

1

Page 29: Module 3: Relational Model

Banking Example

branch (branch_name, branch_city, assets)

customer (customer_name, customer_street, customer_city)

account (account_number, branch_name, balance)

loan (loan_number, branch_name, amount)

depositor (customer_name, account_number)

borrower (customer_name, loan_number)

Page 30: Module 3: Relational Model

Cartesian-Product Operation• Notation r x s• Used to combine information from 2 relations. • Defined as:

r x s = {t q | t r and q s}

• Assume that attributes of r(R) and s(S) are disjoint. (That is, R S = ).

• If attributes of r(R) and s(S) are not disjoint, then renaming must be used.

• Eg if the relation r=borrower*loan then (borrower.customer_name, borrower.loan_number,

loan.loan_number, loan.branch_name, loan.amount)

Page 31: Module 3: Relational Model

Cartesian-Product Operation – ExampleRelations r, s:

r x s:

A B

1

2

A B

11112222

C D

1010201010102010

E

aabbaabb

C D

10102010

E

aabbr

s

Page 32: Module 3: Relational Model

To find names of all customers at “Perryridge branch

• branch_name = “Perryridge” (borrower * loan)

{This will display all the customers who do not have a loan at the Perryridge branch)

• ( borrower.loan_number=loan.loan_number

( branch_name = “Perryridge” (borrower * loan))

{This will display all the customers who has a loan in Perryridge branch }• customer_name ( borrower.loan_number=loan.loan_number

( branch_name = “Perryridge” (borrower * loan)))

{This will display the customer names of all customers who have loan in Perryridge branch}

Page 33: Module 3: Relational Model

Cartesian-Product Operation

• To get only those customers who are in Perryridge customer_name ( borrower.loan_number=loan.loan_number

( branch_name = “Perryridge” (borrower * loan)))

• Select borrower.customer_name from loan, borrower where borrower.loan_number=loan.loan_numbar and borrower.branch_name=“Perryridge”

Page 34: Module 3: Relational Model

Customer-name

Adams

Hayes

Page 35: Module 3: Relational Model

Rename Operation• Allows us to name, and therefore to refer to, the results of relational-algebra

expressions.• Allows us to refer to a relation by more than one name.• Example:

x (E)

returns the expression E under the name X• If a relational-algebra expression E has arity n, then

returns the result of expression E under the name X, and with theattributes renamed to A1 , A2 , …., An .

)(),...,,( 21E

nAAAx

Page 36: Module 3: Relational Model

Example of Rename operation

• Find the names of all customers who live on the same street and in the same city as Smith.

1. Obtain smith’s street and city

2. smith-addr is created using a rename operation on the previous expression

customer.street,customer.city (customer.name =“Smith” (customer))

customer.customer.street=smith-addr.street^customer.customer.city=smith-addr.city(customer* smith-addr(street,city)

(customer.street,customer.city (customer.name =“Smith” (customer))

Page 37: Module 3: Relational Model

3. From this the names of customers who live on the same street and in the same city as Smith is computed.

customer.customer-name( customer.customer.street=smith-addr.street^customer.customer.city=smith-addr.city(customer* smith-

addr(street,city)(customer.street,customer.city (customer.name =“Smith” (customer)))))

Page 38: Module 3: Relational Model

Banking Examplebranch (branch_name, branch_city, assets)

customer (customer_name, customer_street, customer_city)

account (account_number, branch_name, balance)

loan (loan_number, branch_name, amount)

depositor (customer_name, account_number)

borrower (customer_name, loan_number)

Page 39: Module 3: Relational Model

Example Queries• Find all loans of over $1200

Find the loan number for each loan of an amount greater than $1200

amount > 1200 (loan)

loan_number (amount > 1200 (loan))

Find the names of all customers who have a loan, an account, or both, from the bank

customer_name (borrower) customer_name (depositor)

Page 40: Module 3: Relational Model

Example Queries• Find the names of all customers who have a loan at the Perryridge branch.

Find the names of all customers who have a loan at the Perryridge branch but do not have an account at any branch of the bank.

customer_name (branch_name = “Perryridge”

(borrower.loan_number = loan.loan_number(borrower x loan))) –

customer_name(depositor)

customer_name (branch_name=“Perryridge”

(borrower.loan_number = loan.loan_number(borrower x loan)))

Page 41: Module 3: Relational Model

Example Queries- Example of Renaming• Find the largest account balance

– Strategy:• Compute first the temporary relation consisting of those balances that are not the largest.

– Rename account relation as d so that we can compare each account balance with all others• Use set difference to find those account balances that were not found in the earlier step.

– The output of step 1 is account.balance

(account.balance < d.balance (account x d (account)))

The output after step 2

balance(account) - account.balance

(account.balance < d.balance (account x d (account)))

Page 42: Module 3: Relational Model

(SELECT A.SAL FROM EMP A) MINUS (SELECT A.SAL FROM EMP A,EMP B WHERE A.SAL<B. SAL);

Page 43: Module 3: Relational Model

Formal Definition• A basic expression in the relational algebra consists of either one of the

following:– A relation in the database– A constant relation {(A-101, Downtown,500) (A-215, Mianus,700)}

• Let E1 and E2 be relational-algebra expressions; the following are all relational-algebra expressions:

– E1 E2

– E1 – E2

– E1 x E2

– p (E1), P is a predicate on attributes in E1

– s(E1), S is a list consisting of some of the attributes in E1

– x (E1), x is the new name for the result of E1

Page 44: Module 3: Relational Model

Additional OperationsWe define additional operations that do not add any power to therelational algebra, but that simplify common queries.

• Set intersection• Natural join• Division• Assignment

Page 45: Module 3: Relational Model

Set-Intersection Operation• Notation: r s• Defined as:• r s = { t | t r and t s }• Assume:

– r, s have the same arity – attributes of r and s are compatible

• Note: r s = r – (r – s)• Example all customers who have both a loan and an account

customer_name (borrwer) customer_name (depositor)

Page 46: Module 3: Relational Model

Set-Intersection Operation – Example• Relation r, s:

• r s

A B

121

A B

23

r s

A B

2

Page 47: Module 3: Relational Model

Notation: r s

Natural-Join Operation

• Let r and s be relations on schemas R and S respectively. Then, r s is a relation on schema R S obtained as follows:

• The natural join of r and s, denoted by r s, is a relation on schema R S formally defined as follows:

• r s= R B (r..A1=s.A1 r.A2=s.A2……… (r x s))

• Example:R = (A, B, C, D)S = (E, B, D)– Result schema = (A, B, C, D, E)– r s is defined as:

r.A, r.B, r.C, r.D, s.E (r.B = s.B r.D = s.D (r x s))

Page 48: Module 3: Relational Model

Natural Join Operation – Example• Relations r, s:

A B

12412

C D

aabab

B

13123

D

aaabb

E

r

A B

11112

C D

aaaab

E

s

r s

Page 49: Module 3: Relational Model

Natural-Join Operation

If we want to find out the names and work place of employees we have to join tables emp and deptSELECT emp.empno, emp.ename, dept.locations from emp, deptwhere emp.deptno=dept.deptno;empno,ename,dept.loc (emp.deptno = dept.deptno)

Page 50: Module 3: Relational Model

Division Operation• Notation: • Suited to queries that include the phrase “for all”.• Find all customers who have an account at all the branches located

in Brooklyn. r1= branch_name (branch_city=“Brooklyn” (branch)

• All (customer_name, branch-name) • [NOTE:- SQL does not directly support division]

r s

Page 51: Module 3: Relational Model

Division Operation – Example Relations r, s:

r s: A

B

1

2

A B

12311134612

r

s

Page 52: Module 3: Relational Model

Another Division ExampleA B

aaaaaaaa

C D

aabababb

E

11113111

Relations r, s:

r s:

D

ab

E

11

A B

aa

C

r

s

Page 53: Module 3: Relational Model

Assignment Operation• The assignment operation () provides a convenient way to express complex

queries. – Write query as a sequential program consisting of

• a series of assignments • followed by an expression whose value is displayed as a result of the

query.– Assignment must always be made to a temporary relation variable.

• Example: Write r s as

temp1 R-S (r )

temp2 R-S ((temp1 x s ) – R-S,S (r ))

result = temp1 – temp2

– The result to the right of the is assigned to the relation variable on the left

of the .

– May use variable in subsequent expressions.

Page 54: Module 3: Relational Model

Bank Example Queries Find the names of all customers who have a loan and an account at bank.

customer_name (borrower) customer_name (depositor)

• Find the name of all customers who have a loan at the bank and the loan amount

customer_name, loan_number, amount (borrower loan)

Page 55: Module 3: Relational Model

Query 1

customer_name (branch_name = “Downtown” (depositor account ))

customer_name (branch_name = “Uptown” (depositor account))

Query 2

customer_name, branch_name (depositor account)

temp(branch_name) ({(“Downtown” ), (“Uptown” )})

Note that Query 2 uses a constant relation.

Bank Example Queries• Find all customers who have an account from at least the “Downtown” and

the Uptown” branches.

Page 56: Module 3: Relational Model

• Find all customers who have an account at all branches located in Brooklyn city.

Bank Example Queries

customer_name, branch_name (depositor account)

branch_name (branch_city = “Brooklyn” (branch))

Page 57: Module 3: Relational Model

Extended Relational-Algebra Operations

• Generalized Projection• Aggregate Functions• Outer Join

Page 58: Module 3: Relational Model

Generalized Projection• Extends the projection operation by allowing arithmetic functions to be used

in the projection list.

• E is any relational-algebra expression

• Each of F1, F2, …, Fn are are arithmetic expressions involving constants and

attributes in the schema of E.• Given relation credit_info(customer_name, limit, credit_balance), find how

much more each person can spend: customer_name, limit – credit_balance (credit_info)

customer_name, limit – credit_balance as credit_available(credit_info)

)( ,...,,21

EnFFF

Page 59: Module 3: Relational Model

Aggregate Functions and Operations• Aggregation function takes a collection of values and returns a single value as

a result.avg: average valuemin: minimum valuemax: maximum valuesum: sum of valuescount: number of values

Multisets are collections on which aggregate functions operate and have have multiple occurrences of a value.

• Aggregate operation in relational algebra

E is any relational-algebra expression– G1, G2 …, Gn is a list of attributes on which to group (can be empty)– Each Fi is an aggregate function– Each Ai is an attribute name

)()(,,(),(,,, 221121E

nnn AFAFAFGGG

Page 60: Module 3: Relational Model

Aggregate Operation – Example• Relation r:

A B

C

7

7

3

10

g sum(c) (r) sum(c )

27

Page 61: Module 3: Relational Model

Aggregate Operation – Example• Relation account grouped by branch-name:

branch_name g sum(balance) (account)

branch_name account_number balance

PerryridgePerryridgeBrightonBrightonRedwood

A-102A-201A-217A-215A-222

400900750750700

branch_name sum(balance)

PerryridgeBrightonRedwood

13001500700

Select branch_name,sum(balance) from account group by branch_name

Page 62: Module 3: Relational Model

Aggregate Functions (Cont.)• Result of aggregation does not have a name

– Can use rename operation to give it a name– For convenience, we permit renaming as part of aggregate operation

branch_name g sum(balance) as sum_balance (account)

Select branch_name,sum(balance) as “sum_balance” from account group by branch_name

Select branch_name,sum(balance) as “sum_balance”, max(balance) as “maximum balance” from account group by branch_name

Page 63: Module 3: Relational Model

Outer Join• An extension of the join operation that avoids loss of information.• Computes the join and then adds tuples form one relation that does not

match tuples in the other relation to the result of the join. • Uses null values:

– null signifies that the value is unknown or does not exist – All comparisons involving null are (roughly speaking) false by definition.

• Outer joins are of 3 types– Left outer join– Right outer join– Full outer join

Page 64: Module 3: Relational Model

Outer Join – Example• Relation loan

Relation borrower

customer_name loan_number

JonesSmithHayes

L-170L-230L-155

300040001700

loan_number amount

L-170L-230L-260

branch_name

DowntownRedwoodPerryridge

Page 65: Module 3: Relational Model

Outer Join – Example• Join

loan borrower

loan_number amount

L-170L-230

30004000

customer_name

JonesSmith

branch_name

DowntownRedwood

JonesSmithnull

loan_number amount

L-170L-230L-260

300040001700

customer_namebranch_name

DowntownRedwoodPerryridge

Left Outer Join

loan borrower

Page 66: Module 3: Relational Model

Outer Join – Example

loan_number amount

L-170L-230L-155

30004000null

customer_name

JonesSmithHayes

branch_name

DowntownRedwoodnull

loan_number amount

L-170L-230L-260L-155

300040001700null

customer_name

JonesSmithnullHayes

branch_name

DowntownRedwoodPerryridgenull

Full Outer Join

loan borrower

Right Outer Join

loan borrower

Page 67: Module 3: Relational Model

Null Values• It is possible for tuples to have a null value, denoted by null, for some of

their attributes

• null signifies an unknown value or that a value does not exist.

• The result of any arithmetic expression involving null is null.

• Aggregate functions simply ignore null values (as in SQL)

• For duplicate elimination and grouping, null is treated like any other value, and two nulls are assumed to be the same (as in SQL)

Page 68: Module 3: Relational Model

SQL> select sal,sal+comm from emp;

SAL SAL+COMM---------- ---------- 800 1600 1900 1250 1750 2975 1250 2650 2850 2450 3000 5000 1500 1500 1100

SAL SAL+COMM---------- ---------- 950 3000 1300

SQL> select sum(comm) from emp;

SUM(COMM)---------- 2200

Page 69: Module 3: Relational Model

Different relational operators deal with null values.

Select If p is true adds to the result, p is false not added to the result.

Project If two tuples in the projection result are exactly the same, and having nulls they are treated as duplicates

Joins Handles in the same manner as that of selection. Union,IntersectionDifference

Treats null as projection operation

Aggregate Treats them as projection

Page 70: Module 3: Relational Model

Modification of the Database• The content of the database may be modified using the following

operations:– Deletion– Insertion– Updating

• All these operations are expressed using the assignment operator.

Page 71: Module 3: Relational Model

Deletion• A delete request is expressed similarly to a query, except instead of

displaying tuples to the user, the selected tuples are removed from the database.

• Can delete only whole tuples; cannot delete values on only particular attributes

• A deletion is expressed in relational algebra by:r r – E

where r is a relation and E is a relational algebra query.

Page 72: Module 3: Relational Model

Deletion Examples• Delete all account records in the Perryridge branch.

Delete all loan records with amount in the range of 0 to 50

loan loan – amount 0and amount 50 (loan)

account account – branch_name = “Perryridge” (account )

Page 73: Module 3: Relational Model

Insertion• To insert data into a relation, we either:

– specify a tuple to be inserted– write a query whose result is a set of tuples to be inserted

• in relational algebra, an insertion is expressed by:r r E

where r is a relation and E is a relational algebra expression.• The insertion of a single tuple is expressed by letting E be a constant relation

containing one tuple.

Page 74: Module 3: Relational Model

Insertion Examples• Insert information in the database specifying that Smith has $1200 in

account A-973 at the Perryridge branch.

Provide as a gift for all loan customers in the Perryridge branch, a $200 savings account. Let the loan number serve as the account number for the new savings account.

account account {(“A-973”, “Perryridge”, 1200)}

depositor depositor {(“Smith”, “A-973”)}

r1 (branch_name = “Perryridge” (borrower loan))

account account loan_number, branch_name, 200 (r1)

depositor depositor customer_name, loan_number (r1)

Page 75: Module 3: Relational Model

Updating• A mechanism to change a value in a tuple without charging all values in the

tuple• Use the generalized projection operator to do this task

• Each Fi is either

– the I th attribute of r, if the I th attribute is not updated, or,– if the attribute is to be updated Fi is an expression, involving only

constants and the attributes of r, which gives the new value for the attribute

)(,,,, 21rr

lFFF

Page 76: Module 3: Relational Model

Update Examples• Make interest payments by increasing all balances by 5 percent.

Pay all accounts with balances over $10,000 6 percent interest and pay all others 5 percent

account account_number, branch_name, balance * 1.06 ( BAL 10000 (account )) account_number, branch_name, balance * 1.05 (BAL 10000 (account))

account account_number, branch_name, balance * 1.05 (account)

Page 77: Module 3: Relational Model

Views

• Certain data has to be hidden from end users.• Suppose a person needs to know a customer’s loan

number and branch name but has no need to see the loan amount.– customer_name,loan_number, branch_name (borrower loan))

• A view can be created using the syntaxCREATE VIEW customer_view AS customer_name,loan_number,

branch_name (borrower loan))

Page 78: Module 3: Relational Model

Views Contd.

• Once view is defined, we can use view name to refer to the virtual relation that the view generates.

• customer_name,loan_number, branch_name (customer_view)

Page 79: Module 3: Relational Model

Is view and assignment operator the same?

• No• Y?• Changes to

Page 80: Module 3: Relational Model

End of Module 3

Page 81: Module 3: Relational Model

Home Work

Page 82: Module 3: Relational Model

Figure 2.3. The branch relation

Page 83: Module 3: Relational Model

Figure 2.6: The loan relation

Page 84: Module 3: Relational Model

Figure 2.7: The borrower relation

Page 85: Module 3: Relational Model

Figure 2.9Result of branch_name = “Perryridge” (loan)

Page 86: Module 3: Relational Model

Figure 2.10: Loan number and the amount of

the loan

Page 87: Module 3: Relational Model

Figure 2.11: Names of all customers who have either an

account or an loan

Page 88: Module 3: Relational Model

Figure 2.12: Customers with an account but no

loan

Page 89: Module 3: Relational Model

Figure 2.13: Result of borrower |X| loan

Page 90: Module 3: Relational Model

Figure 2.15

Page 91: Module 3: Relational Model

Figure 2.16

Page 92: Module 3: Relational Model

Figure 2.17Largest account balance in the

bank

Page 93: Module 3: Relational Model

Figure 2.18: Customers who live on the same street and in the

same city as Smith

Page 94: Module 3: Relational Model

Figure 2.19: Customers with both an account and a loan at the bank

Page 95: Module 3: Relational Model

Figure 2.20

Page 96: Module 3: Relational Model

Figure 2.21

Page 97: Module 3: Relational Model

Figure 2.22

Page 98: Module 3: Relational Model

Figure 2.23

Page 99: Module 3: Relational Model

Figure 2.24: The credit_info relation

Page 100: Module 3: Relational Model

Figure 2.25

Page 101: Module 3: Relational Model

Figure 2.26: The pt_works relation

Page 102: Module 3: Relational Model

Figure 2.27The pt_works relation after

regrouping

Page 103: Module 3: Relational Model

Figure 2.28

Page 104: Module 3: Relational Model

Figure 2.29

Page 105: Module 3: Relational Model

Figure 2.30The employee and ft_works

relations

Page 106: Module 3: Relational Model

Figure 2.31

Page 107: Module 3: Relational Model

Figure 2.32

Page 108: Module 3: Relational Model

Figure 2.33

Page 109: Module 3: Relational Model

Figure 2.34