Lecture 8: Relational Algebra

Slides:



Advertisements
Similar presentations
Tallahassee, Florida, 2014 COP4710 Database Systems Relational Algebra Fall 2014.
Advertisements

Lecture 07: Relational Algebra
1 Relational Algebra. Motivation Write a Java program Translate it into a program in assembly language Execute the assembly language program As a rough.
Relational Algebra (end) SQL April 19 th, Complex Queries Product ( pid, name, price, category, maker-cid) Purchase (buyer-ssn, seller-ssn, store,
Relational Algebra Ch. 7.4 – 7.6 John Ortiz. Lecture 4Relational Algebra2 Relational Query Languages  Query languages: allow manipulation and retrieval.
1 Relational Algebra Lecture #9. 2 Querying the Database Goal: specify what we want from our database Find all the employees who earn more than $50,000.
Relational Algebra Maybe -- SQL. Confused by Normal Forms ? 3NF BCNF 4NF If a database doesn’t violate 4NF (BCNF) then it doesn’t violate BCNF (3NF) !
1 Lecture 12: SQL Friday, October 26, Outline Simple Queries in SQL (5.1) Queries with more than one relation (5.2) Subqueries (5.3) Duplicates.
Lecture #3 Functional Dependencies Normalization Relational Algebra Thursday, October 12, 2000.
1 Lecture 07: Relational Algebra. 2 Outline Relational Algebra (Section 6.1)
Embedded SQL Direct SQL is rarely used: usually, SQL is embedded in some application code. We need some method to reference SQL statements. But: there.
Complex Queries (1) Product ( pname, price, category, maker)
Relational Schema Design (end) Relational Algebra Finally, querying the database!
One More Normal Form Consider the dependencies: Product Company Company, State Product Is it in BCNF?
Relation Decomposition A, A, … A 12n Given a relation R with attributes Create two relations R1 and R2 with attributes B, B, … B 12m C, C, … C 12l Such.
Exercises Product ( pname, price, category, maker) Purchase (buyer, seller, store, product) Company (cname, stock price, country) Person( per-name, phone.
Lecture 3: Relational Algebra and SQL Tuesday, March 25, 2008.
Relational Algebra Basic Operations Algebra of Bags.
1 Introduction to Database Systems CSE 444 Lecture 20: Query Execution: Relational Algebra May 21, 2008.
Datalog –Another query language –cleaner – closer to a “logic” notation, prolog – more convenient for analysis – can express queries that are not expressible.
Transactions, Relational Algebra, XML February 11 th, 2004.
CSE 544: Relational Operators, Sorting Wednesday, 5/12/2004.
1 Lecture 7: Normal Forms, Relational Algebra Monday, 10/15/2001.
Relational Algebra 2. Relational Algebra Formalism for creating new relations from existing ones Its place in the big picture: Declartive query language.
Lecture 13: Relational Decomposition and Relational Algebra February 5 th, 2003.
The Relational Model Lecture 16. Today’s Lecture 1.The Relational Model & Relational Algebra 2.Relational Algebra Pt. II [Optional: may skip] 2 Lecture.
1 Lecture 10: Database Design and Relational Algebra Monday, October 20, 2003.
1 CSE544: Lecture 7 XQuery, Relational Algebra Monday, 4/22/02.
Relational Algebra COMP3211 Advanced Databases Nicholas Gibbins
©Silberschatz, Korth and Sudarshan2.1Database System Concepts - 6 th Edition Chapter 8: Relational Algebra.
Ritu CHaturvedi Some figures are adapted from T. COnnolly
Lecture 14: Relational Algebra Projects XML?
Summary of Relational Algebra
Basic Operations Algebra of Bags
Relational Algebra.
CPSC-310 Database Systems
Module 2: Intro to Relational Model
COP4710 Database Systems Relational Algebra.
Fundamental of Database Systems
Relational Algebra at a Glance
06a: SQL-1 The Basics– Select-From-Where
Chapter 2: Intro to Relational Model
Relational Algebra Chapter 4, Part A
Database Management Systems (CS 564)
Relational Algebra 461 The slides for this text are organized into chapters. This lecture covers relational algebra, from Chapter 4. The relational calculus.
Lecture 18 The Relational Model.
Lecture 10: Relational Algebra (continued), Datalog
April 6th – relational algebra
Instructor: Mohamed Eltabakh
Relational Algebra Chapter 4, Sections 4.1 – 4.2
Lecture 4: Updates, Views, Constraints and Other Fun Features
Basic Operations Algebra of Bags
RDBMS RELATIONAL DATABASE MANAGEMENT SYSTEM.
Lecture 9: Relational Algebra (continued), Datalog
Lecture 12: SQL Friday, October 20, 2000.
Lecture 33: The Relational Model 2
Where are we? Until now: Modeling databases (ODL, E/R): all about the schema Now: Manipulating the data: queries, updates, SQL Then: looking inside -
Lecture 4: SQL Thursday, January 11, 2001.
Chapter 2: Intro to Relational Model
Integrity Constraints
Relational Algebra Friday, 11/14/2003.
Lecture 3 Monday, April 8, 2002.
CS639: Data Management for Data Science
Example of a Relation attributes (or columns) tuples (or rows)
Chapter 2: Intro to Relational Model
Terminology Product Attribute names Name Price Category Manufacturer
Lecture 3: Relational Algebra and SQL
Relational Schema Design (end) Relational Algebra SQL (maybe)
Syllabus Introduction Website Management Systems
Lecture 11: Functional Dependencies
Presentation transcript:

Lecture 8: Relational Algebra Wednesday, 10/17/2001

Outline Relational Algebra (4.1) Operations on Bags (4.6)

Querying the Database Goal: specify what we want from our database Find all the employees who earn more than $50,000 and pay taxes in New Jersey. Could write in C++/Java, but bad idea Instead use high-level query languages: Theoretical: Relational Algebra, Datalog Practical: SQL Relational algebra: a basic set of operations on relations that provide the basic principles.

Relational Algebra at a Glance Operators: relations as input, new relation as output Five basic RA operators: Basic Set Operators union, difference (no intersection, no complement) Selection: s Projection: p Cartesian Product: X Derived operators: Intersection, complement Joins (natural,equi-join, theta join, semi-join) When our relations have attribute names: Renaming: r

Set Operations Binary operations Union, difference, intersection Intersection can be expressed in other ways

Set Operations: Union Union: all tuples in R1 or R2 Notation: R1 U R2 R1, R2 must have the same schema R1 U R2 has the same schema as R1, R2 Example: ActiveEmployees U RetiredEmployees

Set Operations: Difference Difference: all tuples in R1 and not in R2 Notation: R1 – R2 R1, R2 must have the same schema R1 - R2 has the same schema as R1, R2 Example AllEmployees - RetiredEmployees

Set Operations: Intersection Difference: all tuples both in R1 and in R2 Notation: R1 R2 R1, R2 must have the same schema R1 R2 has the same schema as R1, R2 Example UnionizedEmployees RetiredEmployees

Selection Returns all tuples which satisfy a condition Notation: sc(R) c is a condition: =, <, >, and, or, not Output schema: same as input schema Find all employees with salary more than $40,000: sSalary > 40000 (Employee)

Find all employees with salary more than $40,000. s Salary > 40000 (Employee)

Projection Unary operation: returns certain columns Eliminates duplicate tuples ! Notation: P A1,…,An (R) Input schema R(B1,…,Bm) Condition: {A1, …, An} {B1, …, Bm} Output schema S(A1,…,An) Example: project social-security number and names: P SSN, Name (Employee)

P SSN, Name (Employee)

Cartesian Product Each tuple in R1 with each tuple in R2 Notation: R1 x R2 Input schemas R1(A1,…,An), R2(B1,…,Bm) Condition: {A1,…,An} {B1,…Bm} = F Output schema is S(A1, …, An, B1, …, Bm) Notation: R1 x R2 Example: Employee x Dependents Very rare in practice; but joins are very often

Renaming Does not change the relational instance Changes the relational schema only Notation: r B1,…,Bn (R) Input schema: R(A1, …, An) Output schema: S(B1, …, Bn) Example: LastName, SocSocNo (Employee)

LastName, SocSocNo (Employee) Renaming Example Employee Name SSN John 999999999 Tony 777777777 LastName, SocSocNo (Employee) LastName SocSocNo John 999999999 Tony 777777777

Derived Operations Intersection is derived: R1 R2 = R1 – (R1 – R2) why ? There is another way to express it (later) Most importantly: joins, in many variants

Natural Join Notation: R1 R2 Input Schema: R1(A1, …, An), R2(B1, …, Bm) Output Schema: S(C1,…,Cp) Where {C1, …, Cp} = {A1, …, An} U {B1, …, Bm} Meaning: combine all pairs of tuples in R1 and R2 that agree on the attributes: {A1,…,An} {B1,…, Bm} (called the join attributes) Equivalent to a cross product followed by selection Example Employee Dependents

Natural Join Example Employee Name SSN John 999999999 Tony 777777777 Dependents SSN Dname 999999999 Emily 777777777 Joe Employee Dependents = PName, SSN, Dname(s SSN=SSN2(Employee x rSSN2, Dname(Dependents)) Name SSN Dname John 999999999 Emily Tony 777777777 Joe

Natural Join R= S= R S= A B X Y Z V B C Z U V W A B C X Z U V Y W

Natural Join Given the schemas R(A, B, C, D), S(A, C, E), what is the schema of R S ? Given R(A, B, C), S(D, E), what is R S ? Given R(A, B), S(A, B), what is R S ?

Theta Join A join that involves a predicate Notation: R1 q R2 where q is a condition Input schemas: R1(A1,…,An), R2(B1,…,Bm) {A1,…An} {B1,…,Bm} = f Output schema: S(A1,…,An,B1,…,Bm) Derived operator: R1 q R2 = s q (R1 x R2)

Eq-join Most frequently used in practice: R1 A=B R2 Natural join is a particular case of eqjoin A lot of research on how to do it efficiently

Semijoin R S = P A1,…,An (R S) Where the schemas are: Input: R(A1,…An), S(B1,…,Bm) Output: T(A1,…,An)

Semijoin Applications in distributed databases: Product(pid, cid, pname, ...) at site 1 Company(cid, cname, ...) at site 2 Query: sprice>1000(Product) cid=cid Company Compute as follows: T1 = sprice>1000(Product) site 1 T2 = Pcid(T1) site 1 send T2 to site 2 (T2 smaller than T1) T3 = T2 Company site 2 (semijoin) send T3 to site 1 (T3 smaller than Company) Answer = T3 T1 site 1 (semijoin)

Relational Algebra Five basic operators, many derived Combine operators in order to construct queries: relational algebra expressions, usually shown as trees

Complex Queries Product ( pid, name, price, category, maker-cid) Purchase (buyer-ssn, seller-ssn, store, pid) Company (cid, name, stock price, country) Person(ssn, name, phone number, city) Note: in Purchase: buyer-ssn, seller-ssn are foreign keys in Person, pid is foreign key in Product; in Product maker-cid is a foreign key in Company Find phone numbers of people who bought gizmos from Fred. Find telephony products that somebody bought

Exercises Product ( pid, name, price, category, maker-cid) Purchase (buyer-ssn, seller-ssn, store, pid) Company (cid, name, stock price, country) Person(ssn, name, phone number, city) Ex #1: Find people who bought telephony products. Ex #2: Find names of people who bought American products Ex #3: Find names of people who bought American products and did not buy French products Ex #4: Find names of people who bought American products and they live in Seattle. Ex #5: Find people who bought stuff from Joe or bought products from a company whose stock prices is more than $50.

Operations on Bags (and why we care) Union: {a,b,b,c} U {a,b,b,b,e,f,f} = {a,a,b,b,b,b,b,c,e,f,f} add the number of occurrences Difference: {a,b,b,b,c,c} – {b,c,c,c,d} = {a,b,b,d} subtract the number of occurrences Intersection: {a,b,b,b,c,c} {b,b,c,c,c,c,d} = {b,b,c,c} minimum of the two numbers of occurrences Selection: preserve the number of occurrences Projection: preserve the number of occurrences (no duplicate elimination) Cartesian product, join: no duplicate elimination Reading assignment: 4.6.2 - 4.6.6

Summary of Relational Algebra Why bother ? Can write any RA expression directly in C++/Java, seems easy. Two reasons: Each operator admits sophisticated implementations (think of , s C) Expressions in relational algebra can be rewritten: optimized

Glimpse Ahead: Efficient Implementations of Operators s(age >= 30 AND age <= 35)(Employees) Method 1: scan the file, test each employee Method 2: use an index on age Which one is better ? Depends a lot… Employees Relatives Iterate over Employees, then over Relatives Iterate over Relatives, then over Employees Sort Employees, Relatives, do “merge-join” “hash-join” etc

Glimpse Ahead: Optimizations Product ( pid, name, price, category, maker-cid) Purchase (buyer-ssn, seller-ssn, store, pid) Person(ssn, name, phone number, city) Which is better: sprice>100(Product) (Purchase scity=seaPerson) (sprice>100(Product) Purchase) scity=seaPerson Depends ! This is the optimizer’s job…

Finally: RA has Limitations ! Cannot compute “transitive closure” Find all direct and indirect relatives of Fred Cannot express in RA !!! Need to write C program Name1 Name2 Relationship Fred Mary Father Joe Cousin Bill Spouse Nancy Lou Sister