Relational Algebra and views

94
1 Relational Algebra and views

description

Relational Algebra and views. Father of Relational Model Edgar F. Codd (1923-2003). PhD from U. of Michigan, Ann Arbor Received Turing Award in 1981. More see http://en.wikipedia.org/wiki/Edgar_Codd. Relational Algebra Defined: Tuple. An ordered set of data values. - PowerPoint PPT Presentation

Transcript of Relational Algebra and views

Page 1: Relational Algebra and views

1

Relational Algebra and views

Page 2: Relational Algebra and views

2

Father of Relational Model Edgar F. Codd (1923-2003)

•PhD from U. of Michigan, Ann Arbor

•Received Turing Award in 1981.

•More see http://en.wikipedia.org/wiki/Edgar_Codd

Page 3: Relational Algebra and views

Relational Algebra Defined:

Tuple• An ordered set of data values.

{ a1 , a2 , a3 , …, an }

Page 4: Relational Algebra and views

Relational Algebra Defined: Relation

• A set of tuples.

{ { a1, a2, a3, … , an }, { b1, b2, b3, … , bn }, { c1, c2, c3 , … , cn }, …………. ………….}

Page 5: Relational Algebra and views

5

Page 6: Relational Algebra and views

Relational Algebra Defined: Algebra

• Any formal mathematical system consisting of a set of objects and operations on those objects.

• Based on operators and a domain of values

• Operators map arguments from domain into another domain value

• Example: x = 3.5 * y

Page 7: Relational Algebra and views

Relational Algebra Defined: Relational Algebra

• An algebra whose objects are relations and whose operators transform relations into other relations.

• Domain: set of relations, i.e., result is another relation

• Basic operators: select, project, union, set difference, Cartesian product (or cross product)

Page 8: Relational Algebra and views

Relational Algebra Defined:

Where is it in DBMS?

parser

SQLRelationalalgebraexpression

OptimizedRelationalalgebraexpression

Query optimizer

Codegenerator

Queryexecutionplan

Executablecode

DBMS

Page 9: Relational Algebra and views

9

Relational Query Languages

• Languages for describing queries on a relational database

• Structured Query LanguageStructured Query Language (SQL)– Predominant application-level query language– Declarative

• Relational AlgebraRelational Algebra– Intermediate language used within DBMS– Procedural

Page 10: Relational Algebra and views

10

Motivation

• SQL is a declarative language that allows the user to express what information they require from the database.

• It does not allow the user to specify how that information will be extracted. This has the benefit from the user's point of view of making SQL much more usable because s/he does not need to get involved in the detailed mechanisms involved in satisfying the query.

Page 11: Relational Algebra and views

11

• Because of this, the responsibility for developing procedures for satisfying queries devolves to the Query Optimiser, which forms part of the DBMS.

• Relational algebra is a mathematical formalism that is used to express queries. It forms the basis of the procedural language of the execution plans, which are generated by the Query Optimiser.

Execution plans specify how to satisfy the query. They list a sequence of procedures which can be applied to the database in order to satisfy the query.

Page 12: Relational Algebra and views

12

• The Relational Algebra consists of a set of fundamental operators that take relations as their operands and return a relation as their result. This means that operators can be composed, ie the output of one operation may be used as input to another operation.

• The relational algebra is a language of expressions that can be evaluated to yield relations. In a similar way, normal algebraic expressions, for example x+5*y, are evaluated to yield numbers. In normal algebra, one expression can be equivalent to another expression, for example, x+5*y = y*5+x.

Page 13: Relational Algebra and views

13

• The operators defined in the Relational Algebra enable the Query Processor of the DBMS to analyse the structure of queries, to generate alternative strategies for solving them, to evaluate the efficiency of competing strategies, and to manipulate the data in the tables in order to generate query results.

Page 14: Relational Algebra and views

14

What is an Algebra?

• A language based on operators and a domain of values• Operators map values taken from the domain into

other domain values• Hence, an expression involving operators and

arguments produces a value in the domain• When the domain is a set of all relations (and the

operators are as described later), we get the relational relational algebraalgebra

• We refer to the expression as a queryquery and the value produced as the queryquery resultresult

Page 15: Relational Algebra and views

15

Relational Algebra

• Domain: set of relations• Basic operators: selectselect, projectproject, unionunion, setset

differencedifference, CartesianCartesian productproduct• Derived operators: set intersectionset intersection, divisiondivision, joinjoin• Procedural: Relational expression specifies query

by describing an algorithm (the sequence in which operators are applied) for determining the result of an expression

Page 16: Relational Algebra and views

16

The Role of Relational Algebra in a DBMS

Page 17: Relational Algebra and views

17

Relational Algebra Operations

Basic Operations:

• SELECTION, σ - Selects the rows, or tuples, from a relation, which satisfy the specified constraints or restrictions

• PROJECTION, π - Selects the specified columns, or attributes, from a relation

• CROSS PRODUCT, X - Combines the tuples from two relations to create new tuples containing attributes from both original relations. Every tuple from one relation is combined with every tuple from the other relation.

Page 18: Relational Algebra and views

18

• UNION, U - creates a new relation containing all the tuples from two relations which have the same structure.

• SET DIFFERENCE, \ - creates a new relation containing tuples from two relations which have the same structure, and where the tuples exist in the first relation but not in the second relation.

Relational Algebra Operations

Page 19: Relational Algebra and views

19

Some additional operations are:

• Intersection “∩ “

• Join “ “

• Renaming “ρ “

Operations take relations as input, and output relations.

Relational Algebra Operations

Page 20: Relational Algebra and views

Operations (Unary):

Selection, Projection

Selection: <condition(s)> (<relation>)

• Picks tuples from the relation

Projection: <attribute-list> (<relation>)• Picks columns from the relation

Page 21: Relational Algebra and views

Operations (Set):

Union, Set Difference

Union: (<relation>) U (<relation>)• New relation contains all tuples from both

relations, duplicate tuples eliminated.

Set Difference: R – S• Produces a relation with tuples that are in R

but NOT in S.

Page 22: Relational Algebra and views

Operations (Set):

Cartesian Product, Intersect

Cartesian Product: R x S• Produces a relation that is concatenation of

every tuple of R with every tuple of S • The Above operations are the 5 fundamental

operations of relational algebra.

Intersection: R S• All tuples that are in both R and S

Page 23: Relational Algebra and views

Operations (Join):

Theta Join, Natural Join

Theta Join: R F S = F (R x S) – Select all tuples from the Cartesian product

of the two relations, matching condition F– When F contains only equality “=“, it is

called Equijoin

– Natural Join: R S– Equijoin with common attributes eliminated

Page 24: Relational Algebra and views

Operations:

Outer Join, Semi Join(left) Outer Join: R S• Natural join relations while preserving all tuples

from the “outer” side -> NULL values incurred.

Semi Join: R F S = A (R F S)• Join two relations and only keeps the attributes

seem in relation R• There are Semi-Theta Join, Semi-Equijoin and

Semi-Natural Join

Page 25: Relational Algebra and views

Operations:

Division• Division: R ÷ S• Produce a relation consist of the set of tuples

from R that matches the combination of every tuple in S R S R÷S

• T1 ← c (R)

• T2 ← c ((SxT1)–R)

• T ← T1 – T2

Page 26: Relational Algebra and views

Translation to SQL

– FROM clause produces Cartesian product (x) of listed tables

– WHERE clause assigns rows to C in sequence and produces table containing only rows

satisfying condition ( sort of like )– SELECT clause retains listed columns ( )

Page 27: Relational Algebra and views

Translation to SQL (Cont.)• SELECT C.CrsName• FROM Course C, Teaching T• WHERE C.CrsCode=T.CrsCode AND T.Sem=‘F2003’

• List CS courses taught in F2003• Tuple variables clarify meaning.• Join condition “C.CrsCode=T.CrsCode”

– eliminates garbage• Selection condition “ T.Sem=‘F2003’ ”

– eliminates irrelevant rows• Equivalent (using natural join) to:

CrsName(Course Sem=‘F2003’ (Teaching) )CrsName (Sem=‘F2003’ (Course Teaching) )

Page 28: Relational Algebra and views

28

Select Operator

• Produce table containing subset of rows of argument table satisfying condition

condition (relation)

• Example:

Person Person Hobby=‘stamps’(PersonPerson)

1123 John 123 Main stamps1123 John 123 Main coins5556 Mary 7 Lake Dr hiking9876 Bart 5 Pine St stamps

1123 John 123 Main stamps9876 Bart 5 Pine St stamps

Id Name Address Hobby Id Name Address Hobby

Page 29: Relational Algebra and views

29

Selection Condition

• Operators: <, , , >, =, • Simple selection condition:

– <attribute> operator <constant>– <attribute> operator <attribute>

• <condition> AND <condition>

• <condition> OR <condition>• NOT <condition>

Page 30: Relational Algebra and views

30

Selection Condition - Examples

Id>3000 OR Hobby=‘hiking’ (PersonPerson)

Id>3000 AND Id <3999 (PersonPerson)

NOT(Hobby=‘hiking’) (PersonPerson)

Hobby‘hiking’ (PersonPerson)

Page 31: Relational Algebra and views

31

Project Operator

• Produces table containing subset of columns of argument table

attribute list(relation)

• Example: PersonPerson Name,Hobby(PersonPerson)

1123 John 123 Main stamps1123 John 123 Main coins5556 Mary 7 Lake Dr hiking9876 Bart 5 Pine St stamps

John stampsJohn coinsMary hikingBart stamps

Id Name Address Hobby Name Hobby

Page 32: Relational Algebra and views

32

Project Operator

1123 John 123 Main stamps1123 John 123 Main coins5556 Mary 7 Lake Dr hiking9876 Bart 5 Pine St stamps

John 123 MainMary 7 Lake DrBart 5 Pine St

Result is a table (no duplicates); can have fewer tuplesthan the original

Id Name Address Hobby Name Address

• Example: PersonPerson Name,Address(PersonPerson)

Page 33: Relational Algebra and views

33

Expressions

1123 John 123 Main stamps1123 John 123 Main coins5556 Mary 7 Lake Dr hiking9876 Bart 5 Pine St stamps

1123 John9876 Bart

Id Name Address Hobby Id Name

PersonPerson

ResultResult

Id, Name ( Hobby=’stamps’ OR Hobby=’coins’ (PersonPerson) )

Page 34: Relational Algebra and views

34

Set Operators

• Relation is a set of tuples, so set operations should apply: , , (set difference)

• Result of combining two relations with a set operator is a relation => all its elements must be tuples having same structure

• Hence, scope of set operations limited to union compatible relationsunion compatible relations

Page 35: Relational Algebra and views

35

Union Compatible Relations

• Two relations are union compatibleunion compatible if– Both have same number of columns– Names of attributes are the same in both– Attributes with the same name in both relations

have the same domain

• Union compatible relations can be combined using unionunion, intersectionintersection, and setset differencedifference

Page 36: Relational Algebra and views

36

Example

Tables: PersonPerson (SSN, Name, Address, Hobby) ProfessorProfessor (Id, Name, Office, Phone)are not union compatible.

But Name (PersonPerson) and Name (ProfessorProfessor)

are union compatible so

Name (PersonPerson) - Name (ProfessorProfessor)

makes sense.

Page 37: Relational Algebra and views

37

Cartesian Product• If RR and SS are two relations, RR SS is the set of all

concatenated tuples <x,y>, where x is a tuple in RR and y is a tuple in SS– RR and SS need not be union compatible.– But RBut R and SS must have distinct attribute names. Why?

• RR SS is expensive to compute. But why?

A B C D A B C D x1 x2 y1 y2 x1 x2 y1 y2 x3 x4 y3 y4 x1 x2 y3 y4 x3 x4 y1 y2 RR SS x3 x4 y3 y4 RR SS

Page 38: Relational Algebra and views

38

Renaming• Result of expression evaluation is a relation• Attributes of relation must have distinct names.

This is not guaranteed with Cartesian product– e.g., suppose in previous example A and C have the

same name

• Renaming operator tidies this up. To assign the names A1, A2,… An to the attributes of the n column relation produced by expression expr use expr [A1, A2, … An]

Page 39: Relational Algebra and views

39

Example

This is a relation with 4 attributes: StudId, CrsCode1, ProfId, CrsCode2

TranscriptTranscript (StudId, CrsCode, Semester, Grade)

TeachingTeaching (ProfId, CrsCode, Semester)

  StudId, CrsCode (TranscriptTranscript)[StudId, CrsCode1]

ProfId, CrsCode(TeachingTeaching) [ProfId, CrsCode2]

Page 40: Relational Algebra and views

40

Derived Operation: Join

A (generalgeneral or thetatheta) join join of R and S is the expression R c S

where join-condition c is a conjunction of terms: Ai oper Bi

in which Ai is an attribute of R; Bi is an attribute of S; and oper is one of =, <, >, , . Q: Any difference between join condition and selection condition?The meaning is:

c (R S) Where join-condition c becomes a select condition cexcept for possible renamings of attributes (next)

Page 41: Relational Algebra and views

41

Join and Renaming

• Problem: R and S might have attributes with the same name – in which case the Cartesian product is not defined

• Solutions: 1. Rename attributes prior to forming the product and

use new names in join-condition´.2. Qualify common attribute names with relation names

(thereby disambiguating the names). For instance: Transcript.Transcript.CrsCodeCrsCode or Teaching.Teaching.CrsCodeCrsCode

– This solution is nice, but doesn’t always work: consider

RR join_condition RR

In RR.A, how do we know which R is meant?

Page 42: Relational Algebra and views

42

Theta Join – Example Employee(Employee(Name,Id,MngrId,SalaryName,Id,MngrId,Salary) Manager(Manager(Name,Id,SalaryName,Id,Salary)

Output the names of all employees that earnmore than their managers.EmployeeEmployee.Name (EmployeeEmployee MngrId=Id AND Employee.Salary> Manager.Salary

ManagerManager)

The join yields a table with attributes:EmployeeEmployee.Name, EmployeeEmployee.Id, EmployeeEmployee.Salary, MngrIdManagerManager.Name, ManagerManager.Id, ManagerManager.Salary

Page 43: Relational Algebra and views

43

Equijoin Join - Example

Name,CrsCode(StudentStudent Id=StudId Grade=‘A’ (TranscriptTranscript))

Id Name Addr Status111 John ….. …..222 Mary ….. …..333 Bill ….. …..444 Joe ….. …..

StudId CrsCode Sem Grade 111 CSE305 S00 B 222 CSE306 S99 A 333 CSE304 F99 A

Mary CSE306Bill CSE304

The equijoin is used veryfrequently since it combinesrelated data in different relations.

StudentStudent TranscriptTranscript

EquijoinEquijoin: Join condition is a conjunction of equalities.

Page 44: Relational Algebra and views

44

Natural Join• Special case of equijoin:

– join condition equates all and only those attributes with the same name (condition doesn’t have to be explicitly stated)

– duplicate columns eliminated from the result

TranscriptTranscript (StudId, CrsCode, Sem, Grade)Teaching (Teaching (ProfId, CrsCode, Sem)

TranscriptTranscript TeachingTeaching = StudId, Transcript.CrsCode, Transcript.Sem, Grade, ProfId

( TranscriptTranscript Transcipt.CrsCode=Teaching.CrsCode

AND Transcirpt.Sem=Teaching.Sem Teaching Teaching ) [StudId, CrsCode, Sem, Grade, ProfId ]

Q: but why natural join is a derived operator? Because…

Page 45: Relational Algebra and views

45

Natural Join (cont’d)

• More generally:RR SS = attr-list (join-cond (RR × SS) )

where attr-list = attributes (RR) attributes (SS)(duplicates are eliminated) and join-cond has the form: R.A1 = S.A1 AND … AND R.An = S.An

where {A1 … An} = attributes(RR) attributes(SS)

Page 46: Relational Algebra and views

46

Natural Join Example

• List all Ids of students who took at least two different courses:

StudId ( CrsCode CrsCode2 ( TranscriptTranscript

TranscriptTranscript [StudId, CrsCode2, Sem2, Grade2] )) We don’t want to join on CrsCode, Sem, and Grade attributes,hence renaming!

Page 47: Relational Algebra and views

47

Division

• Goal: Produce the tuples in one relation, r, that match all tuples in another relation, s– rr (A1, …An, B1, …Bm)

– ss (B1 …Bm)

– rr/ss, with attributes A1, …An, is the set of all tuples <a> such that for every tuple <b> in ss, <a,b> is in rr

• Can be expressed in terms of projection, set difference, and cross-product

Page 48: Relational Algebra and views

48

Division (cont’d)

Page 49: Relational Algebra and views

49

Division - Example• List the Ids of students who have passed all

courses that were taught in spring 2000• Numerator:

– StudId and CrsCode for every course passed by every student:

StudId, CrsCode (Grade ‘F’ (TranscriptTranscript) )

• Denominator:– CrsCode of all courses taught in spring 2000

CrsCode (Semester=‘S2000’ (TeachingTeaching) )

• Result is numerator/denominator

Page 50: Relational Algebra and views

50

Schema for Student Registration System

StudentStudent (Id, Name, Addr, Status)ProfessorProfessor (Id, Name, DeptId)CourseCourse (DeptId, CrsCode, CrsName, Descr)TranscriptTranscript (StudId, CrsCode, Semester, Grade)TeachingTeaching (ProfId, CrsCode, Semester)DepartmentDepartment (DeptId, Name)

Page 51: Relational Algebra and views

51

Query Sublanguage of SQL

• Tuple variable Tuple variable C ranges over rows of CourseCourse.• Evaluation strategy:

– FROM clause produces Cartesian product of listed tables

– WHERE clause assigns rows to C in sequence and produces table containing only rows satisfying condition

– SELECT clause retains listed columns

• Equivalent to: CrsNameDeptId=‘CS’(CourseCourse)

SELECT C.CrsNameFROM CourseCourse CWHERE C.DeptId = ‘CS’

Page 52: Relational Algebra and views

52

Join Queries

• List CS courses taught in S2000• Tuple variables clarify meaning.• Join condition “C.CrsCode=T.CrsCode”

– relates facts to each other• Selection condition “ T.Semester=‘S2000’ ”

– eliminates irrelevant rows• Equivalent (using natural join) to:

SELECT C.CrsNameFROM CourseCourse C, TeachingTeaching TWHERE C.CrsCode=T.CrsCode AND T.Semester=‘S2000’

CrsName(CourseCourse Semester=‘S2000’ (TeachingTeaching) )

CrsName (Sem=‘S2000’ (CourseCourse TeachingTeaching) )

Page 53: Relational Algebra and views

53

Correspondence Between SQL and Relational Algebra

SELECT C.CrsNameFROM CourseCourse C, TeachingTeaching TWHERE C.CrsCode = T.CrsCode AND T.Semester = ‘S2000’

Also equivalent to:CrsName C_CrsCode=T_CrsCode AND Semester=‘S2000’

(CourseCourse [C_CrsCode, DeptId, CrsName, Desc] TeachingTeaching [ProfId, T_CrsCode, Semester])

• This is the simplest evaluation algorithm for SELECT.• Relational algebra expressions are procedural.

Which of the two equivalent expressions is more easily evaluated?

Page 54: Relational Algebra and views

54

Self-join QueriesFind Ids of all professors who taught at least two courses in the same semester:

SELECT T1.ProfIdFROM TeachingTeaching T1, TeachingTeaching T2WHERE T1.ProfId = T2.ProfId AND T1.Semester = T2.Semester AND T1.CrsCode <> T2.CrsCode

Tuple variables are essential in this query!

Equivalent to: ProfId (T1.CrsCodeT2.CrsCode(TeachingTeaching[ProfId, T1.CrsCode, Semester] TeachingTeaching[ProfId, T2.CrsCode, Semester]))

Page 55: Relational Algebra and views

55

Duplicates

• Duplicate rows not allowed in a relation

• However, duplicate elimination from query result is costly and not done by default; must be explicitly requested:

SELECT DISTINCT …..FROM …..

Page 56: Relational Algebra and views

Equality and comparison operators apply to strings (based on lexical ordering)

WHERE S.Name < ‘P’

Use of Expressions

Concatenate operator applies to stringsWHERE S.Name || ‘--’ || S.Address = ….

Expressions can also be used in SELECT clause:

SELECT S.Name || ‘--’ || S.Address AS NmAddFROM StudentStudent S

Page 57: Relational Algebra and views

57

Set Operators

• SQL provides UNION, EXCEPT (set difference), and INTERSECT for union compatible tables

• Example: Find all professors in the CS Department and all professors that have taught CS courses

(SELECT P.Name FROM ProfessorProfessor P, TeachingTeaching T WHERE P.Id=T.ProfId AND T.CrsCode LIKE ‘CS%’)UNION(SELECT P.Name FROM ProfessorProfessor P WHERE P.DeptId = ‘CS’)

Page 58: Relational Algebra and views

58

Nested QueriesList all courses that were not taught in S2000

SELECT C.CrsNameFROM CourseCourse CWHERE C.CrsCode NOT IN (SELECT T.CrsCode --subquery FROM TeachingTeaching T WHERE T.Sem = ‘S2000’)

Evaluation strategy: subquery evaluated once toproduces set of courses taught in S2000. Each row(as C) tested against this set.

Page 59: Relational Algebra and views

59

Correlated Nested Queries Output a row <prof, dept> if prof has taught a course in dept.

(SELECT T.ProfId --subquery FROM TeachingTeaching T, CourseCourse C WHERE T.CrsCode=C.CrsCode AND C.DeptId=D.DeptId --correlation)

SELECT P.Name, D.Name --outer query FROM ProfessorProfessor P, DepartmentDepartment D WHERE P.Id IN -- set of all ProfId’s who have taught a course in D.DeptId

Page 60: Relational Algebra and views

60

Correlated Nested Queries (con’t)

• Tuple variables T and C are local to subquery• Tuple variables P and D are global to subquery• CorrelationCorrelation: subquery uses a global variable, D• The value of D.DeptId parameterizes an evaluation of

the subquery• Subquery must (at least) be re-evaluated for each

distinct value of D.DeptId

• Correlated queries can be expensive to evaluate

Page 61: Relational Algebra and views

61

Division in SQL• Query type: Find the subset of items in one set that

are related to all items in another set• Example: Find professors who taught courses in all

departments– Why does this involve division?

ProfId DeptId DeptId

All department IdsContains row<p,d> if professorp taught acourse in department d

ProfId,DeptId(Teaching Course) / DeptId(Department)

Page 62: Relational Algebra and views

62

Division in SQL

• Strategy for implementing division in SQL: – Find set, A, of all departments in which a

particular professor, p, has taught a course

– Find set, B, of all departments

– Output p if A B, or, equivalently, if B–A is empty

• But how to do this exactly in SQL?

Page 63: Relational Algebra and views

63

Division Solution Sketch (1)SELECT P.IdFROM ProfessorProfessor PWHERE P taught courses in all departments

SELECT P.IdFROM ProfessorProfessor PWHERE there does not exist any department that P has never taught a course

SELECT P.IdFROM ProfessorProfessor PWHERE NOT EXISTS(the departments that P has never taught a course)

Page 64: Relational Algebra and views

64

Division Solution Sketch (1)SELECT P.IdFROM ProfessorProfessor PWHERE NOT EXISTS(the departments that P has never taught a course)

SELECT P.IdFROM ProfessorProfessor PWHERE NOT EXISTS( B: All departments EXCEPT A: the departments that P has ever taught a course)But how do we formulate A and B?

Page 65: Relational Algebra and views

65

Division – SQL Solution in details

SELECT P.IdFROM ProfessorProfessor PWHERE NOT EXISTS (SELECT D.DeptId -- set B of all dept Ids FROM DepartmentDepartment D EXCEPT SELECT C.DeptId -- set A of dept Ids of depts in -- which P taught a course FROM TeachingTeaching T, CourseCourse C WHERE T.ProfId=P.Id -- global variable AND T.CrsCode=C.CrsCode)

Page 66: Relational Algebra and views

66

Aggregates

• Functions that operate on sets:– COUNT, SUM, AVG, MAX, MIN

• Produce numbers (not tables)• Aggregates over multiple rows into one row• Not part of relational algebra (but not hard to add)

SELECT COUNT(*)FROM ProfessorProfessor P

SELECT MAX (Salary)FROM EmployeeEmployee E

Page 67: Relational Algebra and views

67

Aggregates (cont’d)

SELECT COUNT (T.CrsCode)FROM TeachingTeaching TWHERE T.Semester = ‘S2000’

SELECT COUNT (DISTINCT T.CrsCode)FROM TeachingTeaching TWHERE T.Semester = ‘S2000’

Count the number of courses taught in S2000

But if multiple sections of same course are taught, use:

Page 68: Relational Algebra and views

68

Grouping• But how do we compute the number of courses

taught in S2000 per professor?– Strategy 1: Fire off a separate query for each

professor:SELECT COUNT(T.CrsCode)FROM TeachingTeaching TWHERE T.Semester = ‘S2000’ AND T.ProfId =

123456789• Cumbersome• What if the number of professors changes? Add another query?

– Strategy 2: define a special grouping operatorgrouping operator:SELECT T.ProfId, COUNT(T.CrsCode)FROM TeachingTeaching TWHERE T.Semester = ‘S2000’GROUP BY T.ProfId

Page 69: Relational Algebra and views

69

GROUP BY

Values are the same for all rows in same group

Values might be different for rows in the same group, need aggregation!

Page 70: Relational Algebra and views

70

GROUP BY - Example

SELECT T.StudId, AVG(T.Grade), COUNT (*)FROM TranscriptTranscript TGROUP BY T.StudId

TranscriptTranscript

Attributes: –student’s Id –avg grade –number of courses

1234 3.3 41234123412341234

-Finally, each group of rows is aggregated into one row

Page 71: Relational Algebra and views

71

HAVING Clause• Eliminates unwanted groups (analogous to

WHERE clause, but works on groups instead of individual tuples)

• HAVING condition is constructed from attributes of GROUP BY list and aggregates on attributes not in that list

SELECT T.StudId, AVG(T.Grade) AS CumGpa, COUNT (*) AS NumCrsFROM Transcript Transcript TWHERE T.CrsCode LIKE ‘CS%’GROUP BY T.StudIdHAVING AVG (T.Grade) > 3.5

Apply to each group not to the whole table

Page 72: Relational Algebra and views

72

Evaluation of GroupBy with Having

Page 73: Relational Algebra and views

73

Example

• Output the name and address of all seniors on the Dean’s List

SELECT S.Id, S.NameFROM StudentStudent S, TranscriptTranscript TWHERE S.Id = T.StudId AND S.Status = ‘senior’

GROUP BY

HAVING AVG (T.Grade) > 3.5 AND SUM (T.Credit) > 90

S.Id -- wrongS.Id, S.Name -- right

Every attribute that occurs in SELECT clause must also occur in GROUP BY or it must be an aggregate. S.Name does not.

> The DB has not used the information that “S.Id S.Name”.

Page 74: Relational Algebra and views

74

Aggregates: Proper and Improper Usage

SELECT COUNT (T.CrsCode), T. ProfId – makes no sense (in the absence of GROUP BY clause)

SELECT COUNT (*), AVG (T.Grade) – but this is OK

WHERE T.Grade > COUNT (SELECT ….) – aggregate cannot be applied to result of SELECT statement

Page 75: Relational Algebra and views

75

ORDER BY Clause

• Causes rows to be output in a specified order

SELECT T.StudId, COUNT (*) AS NumCrs, AVG(T.Grade) AS CumGpaFROM TranscriptTranscript TWHERE T.CrsCode LIKE ‘CS%’GROUP BY T.StudIdHAVING AVG (T.Grade) > 3.5ORDER BY DESC CumGpa, ASC StudId

Descending Ascending

Page 76: Relational Algebra and views

76

Query Evaluation with GROUP BY, HAVING, ORDER BY

1 Evaluate FROM: produces Cartesian product, A, of tables in FROM list

2 Evaluate WHERE: produces table, B, consisting of rows of A that satisfy WHERE condition

3 Evaluate GROUP BY: partitions B into groups that agree on attribute values in GROUP BY list

4 Evaluate HAVING: eliminates groups in B that do not satisfy HAVING condition

5 Evaluate SELECT: produces table C containing a row for each group. Attributes in SELECT list limited to those in GROUP BY list and aggregates over group

6 Evaluate ORDER BY: orders rows of C

A s

b

e f

o r

e

Page 77: Relational Algebra and views

77

Views• Used as a relation, but rows are not physically

stored. – The contents of a view is computed when it is used

within an SQL statement– Each time it is used (thus computed), the content might

different as underlying base tables might have changed

• View is the result of a SELECT statement over other views and base relations

• When used in an SQL statement, the view definition is substituted for the view name in the statement– As SELECT statement nested in FROM clause

Page 78: Relational Algebra and views

78

View - Example

CREATE VIEW CumGpaCumGpa (StudId, Cum) AS SELECT T.StudId, AVG (T.Grade) FROM TranscriptTranscript T GROUP BY T.StudId

SELECT S.Name, C.CumFROM CumGpaCumGpa C, StudentStudent SWHERE C.StudId = S.StudId AND C.Cum > 3.5

Page 79: Relational Algebra and views

79

View - Substitution

SELECT S.Name, C.CumFROM (SELECT T.StudId, AVG (T.Grade) FROM TranscriptTranscript T

GROUP BY T.StudId) C, StudentStudent SWHERE C.StudId = S.StudId AND C.Cum > 3.5

When used in an SQL statement, the view definition is substituted for the view name in the statement. As SELECT statement nested in FROM clause

Page 80: Relational Algebra and views

80

View Benefits

• Access Control: Users not granted access to base tables. Instead they are granted access to the view of the database appropriate to their needs.– External schemaExternal schema is composed of views.– View allows owner to provide SELECT access

to a subset of columns (analogous to providing UPDATE and INSERT access to a subset of columns)

Page 81: Relational Algebra and views

81

Views – Limiting Visibility

CREATE VIEW PartOfTranscriptPartOfTranscript (StudId, CrsCode, Semester) AS SELECT T. StudId, T.CrsCode, T.Semester -- limit columns FROM TranscriptTranscript T WHERE T.Semester = ‘S2000’ -- limit rows

Give permissions to access data through view:

GRANT SELECT ON PartOfTranscriptPartOfTranscript TO joe

This would have been analogous to:

GRANT SELECT (StudId,CrsCode,Semester) ON TranscriptTranscript TO joe

on regular tables, ifif SQL allowed attribute lists in GRANT SELECT

Grade projected out

Page 82: Relational Algebra and views

82

View Benefits (cont’d)

• Customization: Users need not see full complexity of database. View creates the illusion of a simpler database customized to the needs of a particular category of users

• A view is similar in many ways to a subroutine in standard programming– Can be reused in multiple queries

Page 83: Relational Algebra and views

83

Nulls• Conditions: x op y (where op is <, >, <>, =, etc.)

has value unknownunknown (U) when either x or y is null– WHERE T.cost > T.price

• Arithmetic expression: x op y (where op is +, –, *, etc.) has value NULL if x or y is NULL– WHERE (T. price/T.cost) > 2

• Aggregates: COUNT counts NULLs like any other value; other aggregates ignore NULLs

SELECT COUNT (T.CrsCode), AVG (T.Grade)FROM TranscriptTranscript TWHERE T.StudId = ‘1234’

Page 84: Relational Algebra and views

84

• WHERE clause uses a three-valued logic – T, F, three-valued logic – T, F, U(ndefined) –U(ndefined) – to filter rows. Portion of truth table:

• Rows are discarded if WHERE condition is F(alse) or U(nknown)

• Ex: WHERE T.CrsCode = ‘CS305’ AND T.Grade > 2.5• Q: Why not simply replace each “U” to “F”?

Nulls (cont’d)

C1 C2 C1 AND C2 C1 OR C2T U U TF U F UU U U U

Page 85: Relational Algebra and views

85

Modifying Tables – Insert

• Inserting a single row into a table– Attribute list can be omitted if it is the same as

in CREATE TABLE (but do not omit it)– NULL and DEFAULT values can be specified

INSERT INTO TranscriptTranscript(StudId, CrsCode, Semester, Grade)VALUES (12345, ‘CSE305’, ‘S2000’, NULL)

Page 86: Relational Algebra and views

86

Bulk Insertion• Insert the rows output by a SELECT

INSERT INTO DeansListDeansList (StudId, Credits, CumGpa)SELECT T.StudId, 3 * COUNT (*), AVG(T.Grade) FROM TranscriptTranscript TGROUP BY T.StudIdHAVING AVG (T.Grade) > 3.5 AND COUNT(*) > 30

CREATE TABLE DeansListDeansList (StudId INTEGER,Credits INTEGER,CumGpa FLOAT,PRIMARY KEY StudId )

Page 87: Relational Algebra and views

87

Modifying Tables – Delete • Similar to SELECT except:

– No project list in DELETE clause– No Cartesian product in FROM clause (only 1 table

name)– Rows satisfying WHERE clause (general form,

including subqueries, allowed) are deleted instead of output

DELETE FROM TranscriptTranscript TWHERE T.Grade IS NULL AND T.Semester <> ‘S2000’

Page 88: Relational Algebra and views

88

Modifying Data - Update

• Updates rows in a single table

• All rows satisfying WHERE clause (general form, including subqueries, allowed) are updated

UPDATE EmployeeEmployee ESET E.Salary = E.Salary * 1.05WHERE E.Department = ‘R&D’

Page 89: Relational Algebra and views

89

Updating Views

• Question: Since views look like tables to users, can they be updated?

• Answer: Yes – a view update changes the underlying base table to produce the requested change to the view

CREATE VIEW CsRegCsReg (StudId, CrsCode, Semester) ASSELECT T.StudId, T. CrsCode, T.SemesterFROM TranscriptTranscript TWHERE T.CrsCode LIKE ‘CS%’ AND T.Semester=‘S2000’

Page 90: Relational Algebra and views

90

Updating Views - Problem 1

• Question: What value should be placed in attributes of underlying table that have been projected out (e.g., Grade)?

• Answer: NULL (assuming null allowed in the missing attribute) or DEFAULT

INSERT INTO CsRegCsReg (StudId, CrsCode, Semester)VALUES (1111, ‘CSE305’, ‘S2000’)Tuple is in the VIEW

Page 91: Relational Algebra and views

91

Updating Views - Problem 2

• Problem: New tuple not in view

• Solution: Allow insertion (assuming the WITH CHECK OPTION clause has not been appended to the CREATE VIEW statement)

INSERT INTO CsRegCsReg (StudId, CrsCode, Semester)VALUES (1111, ‘ECO105’, ‘S2000’)

Page 92: Relational Algebra and views

92

Updating Views - Problem 3

• Update to a view might not uniquely specify the change to the base table(s) that results in the desired modification of the view (ambiguity)

CREATE VIEW ProfDeptProfDept (PrName, DeName) ASSELECT P.Name, D.NameFROM ProfessorProfessor P, DepartmentDepartment DWHERE P.DeptId = D.DeptId

Page 93: Relational Algebra and views

93

Updating Views - Problem 3 (cont’d)

• Tuple <Smith, CS> can be deleted from ProfDeptProfDept by:– Deleting row for Smith from ProfessorProfessor (but this

is inappropriate if he is still at the University)– Deleting row for CS from DepartmentDepartment (not

what is intended)– Updating row for Smith in ProfessorProfessor by setting

DeptId to null (seems like a good idea, but how would the computer know?)

Page 94: Relational Algebra and views

94

Updating Views – Restrictions• Updatable views are restricted to those in which

– No Cartesian product in FROM clause, single table

– no aggregates, GROUP BY, HAVING– …

For example, if we allowed:

CREATE VIEW AvgSalaryAvgSalary (DeptId, Avg_Sal )

AS SELECT E.DeptId, AVG(E.Salary) FROM EmployeeEmployee E GROUP BY E.DeptId

then how do we handle:

UPDATE AvgSalaryAvgSalary SET Avg_Sal = 1.1 * Avg_Sal