COP Introduction to Database Structures

Slides:



Advertisements
Similar presentations
SQL: The Query Language Part 2
Advertisements

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Programming, Triggers Chapter 5 Modified by Donghui Zhang.
Introduction to Database Systems 1 SQL: The Query Language Relation Model : Topic 4.
1 SQL: Structured Query Language (‘Sequel’) Chapter 5.
CS 166: Database Management Systems
SQL: Queries, Constraints, Triggers
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Constraints, Triggers Chapter 5.
Database Management Systems 1 Raghu Ramakrishnan SQL: Queries, Programming, Triggers Chpt 5.
SQL.
SQL: The Query Language Jianlin Feng School of Software SUN YAT-SEN UNIVERSITY courtesy of Joe Hellerstein and etc for some slides.
Database Management Systems, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Programming, Triggers Chapter 5.
CS 405G: Introduction to Database Systems
CMPT 258 Database Systems SQL: Queries, Constraints, Triggers (Chapter 5) Part II home.manhattan.edu/~tina.tian.
M ATH IN SQL. 222 A GGREGATION O PERATORS Operators on sets of tuples. Significant extension of relational algebra. SUM ( [DISTINCT] A): the sum of all.
SQL Review.
1 SQL: Structured Query Language (‘Sequel’) Chapter 5.
CMPT 354, Simon Fraser University, Fall 2008, Martin Ester 90 Database Systems I SQL Queries.
FALL 2004CENG 351 File Structures and Data Management1 SQL: Structured Query Language Chapter 5.
Rutgers University SQL: Queries, Constraints, Triggers 198:541 Rutgers University.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Constraints, Triggers Chapter 5.
1 SQL: Structured Query Language Chapter 5. 2 SQL and Relational Calculus relationalcalculusAlthough relational algebra is useful in the analysis of query.
CSC343 – Introduction to Databases - A. Vaisman1 SQL: Queries, Programming, Triggers.
Chapter 5.  Data Manipulation Language (DML): subset of SQL which allows users to create queries and to insert, delete and modify rows.  Data Definition.
INFS614 - Lecture week 9 1 More on SQL Lecture Week 9 INFS 614, Fall 2008.
Introduction to SQL Basics; Christoph F. Eick & R. Ramakrishnan and J. Gehrke 1 Introduction to SQL Basics --- SQL in 45 Minutes Chapter 5.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Constraints, Triggers Chapter 5.
CSC 411/511: DBMS Design Dr. Nan WangCSC411_L6_SQL(1) 1 SQL: Queries, Constraints, Triggers Chapter 5 – Part 1.
SQL Examples CS3754 Class Note 11 CS3754 Class Note 11, John Shieh,
SQL 2 Introduction Structured Query Language (SQL): the most widely used commercial relational database language Originally.
Unit 5/COMP3300/ SQL: Queries, Programming, Triggers Chapter 5.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Constraints, Triggers Chapter 5.
SQL: Queries, Programming, Triggers. Example Instances We will use these instances of the Sailors and Reserves relations in our examples. If the key for.
ICS 321 Fall 2009 SQL: Queries, Constraints, Triggers Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 9/8/20091Lipyeow.
1 Database Systems ( 資料庫系統 ) October 24, 2005 Lecture #5.
1 SQL: Queries, Constraints, Triggers Chapter 5. 2 Example Instances R1 S1 S2  We will use these instances of the Sailors and Reserves relations in our.
Introduction to SQL ; Christoph F. Eick & R. Ramakrishnan and J. Gehrke 1 Using SQL as a Query Language COSC 6340.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 SQL: Queries, Constraints, Triggers Chapter 5.
CMPT 258 Database Systems SQL Queries (Chapter 5).
1 SQL: Queries, Constraints, Triggers Chapter 5. 2 Overview: Features of SQL  Data definition language: used to create, destroy, and modify tables and.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 5 SQL.
1 SQL: The Query Language (Part II). 2 Expressions and Strings v Illustrates use of arithmetic expressions and string pattern matching: Find triples (of.
1 SQL: Structured Query Language (‘Sequel’) Chapter 5.
SQL: The Query Language Part 1 R &G - Chapter 5 The important thing is not to stop questioning. Albert Einstein.
1 SQL: The Query Language. 2 Example Instances R1 S1 S2 v We will use these instances of the Sailors and Reserves relations in our examples. v If the.
Database Management Systems 1 Raghu Ramakrishnan SQL: Queries, Programming, Triggers Chpt 5 Jianping Fan.
SQL: The Query Language Part 1 R&G - Chapter 5 1.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Basic SQL Queries.
CENG 351 File Structures and Data Management1 SQL: Structured Query Language Chapter 5.
1 CS122A: Introduction to Data Management Lecture 9 SQL II: Nested Queries, Aggregation, Grouping Instructor: Chen Li.
1 SQL: The Query Language. 2 Example Instances R1 S1 S2 v We will use these instances of the Sailors and Reserves relations in our examples.
1 Relational Calculus ♦ Comes in two flavors: Tuple relational calculus (TRC) and Domain relational calculus (DRC). ♦ Calculus has variables, constants,
SQL: Queries, Constraints, Triggers
Basic SQL Queries Go over example queries, like 10 > ALL.
01/31/11 SQL Examples Edited by John Shieh CS3754 Classnote #10.
SQL The Query Language R & G - Chapter 5
Database Systems October 14, 2009 Lecture #5.
Database Systems (資料庫系統)
Basic SQL Lecture 6 Fall
SQL: Queries, Constraints, Triggers
SQL: The Query Language
SQL: Queries, Programming, Triggers
Database Applications (15-415) SQL-Part II Lecture 9, February 04, 2018 Mohammad Hammoud.
CS 405G: Introduction to Database Systems
SQL: Queries, Constraints, Triggers
SQL: The Query Language Part 1
SQL: Structured Query Language
SQL: Queries, Programming, Triggers
SQL: Queries, Constraints, Triggers
SQL: The Query Language (Part III)
SQL: Queries, Programming, Triggers
Presentation transcript:

COP 3540 - Introduction to Database Structures SQL I

Database Language Structured Query Language (SQL) is the most widely used commercial relational database languages. Database Language allows a user to: create the database and relation structures; perform basic data management tasks, such as the insertion, modification, and deletion of data from the relations; perform both simple and complex queries.

SQL Two major components: Data Definition Language (DDL) for defining the database structure and controlling access to the data Data Manipulation Language (DML) for retrieving and updating data.

Data Manipulation Language (DML) SELECT – to query data in the database INSERT – to insert data into a table UPDATE – to update data in a table DELETE – to delete data from a table

Data Manipulation Language (DML) SELECT [DISTINCT] target-list FROM relation-list WHERE qualification Relation-list A list of relation (i.e., tables) names (possibly with a range-variable after each name). Target-list A list of attributes of relations in relation-list Qualification Comparisons (Attr op const or Attr1 op Attr2, where op is one of ) combined using AND, OR and NOT. DISTINCT is an optional keyword indicating that the answer should not contain duplicates. Default is that duplicates are not eliminated!

SQL Logical Operators

Conceptual Evaluation Strategy Semantics of SQL query defined in terms of the following conceptual evaluation strategy: Compute the cross-product of relation-list. Discard resulting tuples if they fail qualifications. Delete attributes that are not in target-list. If DISTINCT is specified, eliminate duplicate rows. This strategy is probably the least efficient way to compute a query! An optimizer will find more efficient strategies to compute the same answers.

Example Instances We will use these tables, Sailors, Reserves, and Boats.

Example Instances Sailors

Example Instances Reserves

Example Instances Boats

(Question) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.age=35 Sailors

(Answer) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.age=35

(Question) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.age=35 AND S.rating=10 Sailors

(Answer) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.age=35 AND S.rating=10

(Question) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.rating <> 10 Sailors

(Answer) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.rating <> 10

(Question) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.rating BETWEEN 5 AND 10 Sailors

(Answer) Example of SQL Comparison SELECT S.sname FROM Sailors S WHERE S.rating BETWEEN 5 AND 10 SELECT S.sname FROM Sailors S WHERE S.rating >= 5 AND S.rating <= 10

(Question) Example of SQL Comparison SELECT S.sid, S.sname, S.age, S.age FROM Sailors S WHERE S.age=35 AND S.rating=10 Sailors

(Answer) Example of SQL Comparison SELECT S.sid, S.sname, S.age, S.age FROM Sailors S WHERE S.age=35 AND S.rating=10 SELECT * FROM Sailors S WHERE S.age=35 AND S.rating=10

(Question) Example of SQL Comparison SELECT S.sid, S.sname, S.age, S.age FROM Sailors S WHERE S.age < 30 AND S.rating > 9 Sailors

(Answer) Example of SQL Comparison SELECT S.sid, S.sname, S.age, S.age FROM Sailors S WHERE S.age < 30 AND S.rating > 9

(Question) Example of Join Operation SELECT S.sname, R.bid FROM Sailors S, Reserves R WHERE S.sid=R.sid AND R.bid=103 Sailors Reserves

(Answer) Example of Join Operation SELECT S.sname, R.bid FROM Sailors S, Reserves R WHERE S.sid=R.sid AND R.bid=103

A Note on Range Variables The previous query can also be written as: SELECT sname FROM Sailors, Reserves WHERE Sailors.sid=Reserves.sid AND bid=103 It is good style, however, to use variables always! OR SELECT S.sname FROM Sailors S, Reserves R WHERE S.sid=R.sid AND bid=103

Example SELECT S.sid, S.sname FROM Sailors S, Reserves R Retrieve the sids and names for sailors who’ve reserved at least one boat. SELECT S.sid, S.sname FROM Sailors S, Reserves R WHERE S.sid = R.sid

Example SELECT distinct S.sid, S.sname FROM Sailors S, Reserves R Retrieve the sids and names for sailors who’ve reserved at least one boat SELECT distinct S.sid, S.sname FROM Sailors S, Reserves R WHERE S.sid = R.sid

Expressions and Strings SELECT S.age, S.age - 5, 2 * S.age AS age2 FROM Sailors S WHERE S.sname LIKE ‘B_%B’ AS can be used to create a temporary name for columns. LIKE is used for string matching _ stands for any one character % stands for 0 or more arbitrary characters.

(Question) Expressions and Strings SELECT S.sid, S.sname AS test FROM Sailors S WHERE S.sname LIKE ‘%or%’ Sailors

(Question) Expressions and Strings SELECT S.sid, S.sname AS test FROM Sailors S WHERE S.sname LIKE ‘%or%’ Sailors

(Answer) Expressions and Strings SELECT S.sid, S.sname AS name FROM Sailors S WHERE S.sname LIKE ‘%or%’

Set Operators

Set Operators

Set Operators

UNION UNION: Can be used to compute the union of any two union-compatible sets of tuples (which are themselves the result of SQL queries). SELECT R.sid FROM Boats B, Reserves R WHERE R.bid=B.bid AND (B.color=‘red’ OR B.color=‘green’) SELECT R.sid FROM Boats B, Reserves R WHERE R.bid=B.bid AND B.color=‘red’ UNION WHERE R.bid=B.bid AND B.color=‘green’

INTERSECTION INTERSECT: Can be used to compute the intersection of any two union-compatible sets of tuples. SELECT S.sid FROM Sailors S, Boats B, Reserves R WHERE S.sid=R.sid AND R.bid=B.bid AND B.color=‘red’ INTERSECT AND B.color=‘green’

Nested Queries Find names of sailors who’ve reserved boat #103: SELECT S.sname FROM Sailors S WHERE S.sid IN (SELECT R.sid FROM Reserves R WHERE R.bid=103) Find names of sailors who never reserved boat #103: SELECT S.sname FROM Sailors S WHERE S.sid NOT IN (SELECT R.sid FROM Reserves R WHERE R.bid=103)

Nested Queries with Correlation Find names of sailors who’ve reserved boat #103: SELECT S.sname FROM Sailors S WHERE EXISTS ( SELECT * FROM Reserves R WHERE R.bid=103 AND S.sid=R.sid)

More on Set-Comparison Operators Find the names of sailors whose rating is greater than that of some sailor called Horatio: SELECT S.sname FROM Sailors S WHERE S.rating > ANY ( SELECT S2.rating FROM Sailors S2 WHERE S2.sname=‘Horatio’)

More on Set-Comparison Operators Find the names of sailors whose rating is greater than that of some sailor called Horatio: SELECT S.sname FROM Sailors S WHERE S.rating > ALL ( SELECT S2.rating FROM Sailors S2 WHERE S2.sname=‘Horatio’)

Rewriting INTERSECT Queries Using IN Find sids of sailors who’ve reserved both a red and a green boat: SELECT R1.sid FROM Boats B1, Reserves R1 WHERE R1.bid=B1.bid AND B1.color=‘red’ AND R1.sid IN ( SELECT R2.sid FROM Boats B2, Reserves R2 WHERE R2.bid=B2.bid AND B2.color=‘green’)

Division in SQL Find sailors who’ve reserved all boats. SELECT S.sname FROM Sailors S WHERE NOT EXISTS ((SELECT B.bid FROM Boats B) EXCEPT (SELECT R.bid FROM Reserves R WHERE R.sid=S.sid)) Let’s do it the hard way, without EXCEPT: SELECT S.sname FROM Sailors S WHERE NOT EXISTS (SELECT B.bid FROM Boats B WHERE NOT EXISTS ( SELECT R.bid FROM Reserves R WHERE R.bid=B.bid AND R.sid=S.sid)) Sailors S such that ... there is no boat B without ... a Reserves tuple showing S reserved B

Aggregation Operators Significant extension of relational algebra. COUNT (*) COUNT ( [DISTINCT] A) SUM ( [DISTINCT] A) AVG ( [DISTINCT] A) MAX (A) MIN (A) SELECT COUNT (*) FROM Sailors S SELECT AVG (S.age) FROM Sailors S WHERE S.rating=10 SELECT S.sname FROM Sailors S WHERE S.rating= (SELECT MAX (S2.rating) FROM Sailors S2) single column SELECT COUNT ( DISTINCT S.rating ) FROM Sailors S WHERE S.sname=‘Bob’ SELECT AVG ( DISTINCT S.age) FROM Sailors S WHERE S.rating=10

Aggregation Operators

Find name and age of the oldest sailor(s) The first query is illegal! (We’ll look into the reason a bit later, when we discuss GROUP BY.) The third query is equivalent to the second query, and is allowed in the SQL/92 standard, but is not supported in some systems. SELECT S.sname, MAX (S.age) FROM Sailors S SELECT S.sname, S.age FROM Sailors S WHERE S.age = (SELECT MAX (S2.age) FROM Sailors S2) SELECT S.sname, S.age FROM Sailors S WHERE (SELECT MAX (S2.age) FROM Sailors S2) = S.age

GROUP BY and HAVING So far, we’ve applied aggregate operators to all (qualifying) tuples. Sometimes, we want to apply them to each of several groups of tuples. Consider: Find the age of the youngest sailor for each rating level. In general, we don’t know how many rating levels exist, and what the rating values for these levels are! Suppose we know that rating values go from 1 to 10; we can write 10 queries that look like this (!): SELECT MIN (S.age) FROM Sailors S WHERE S.rating = i For i = 1, 2, ... , 10:

GROUP BY Department SELECT C.department, count(*), sum (SKU), avg (SKU) FROM Catalog C GROUP BY department

GROUP BY Department SELECT S.rating, count(*), sum (age), max (age), min (age) FROM Sailors S GROUP BY S.rating

SELECT S.rating, count(*), sum (age), max (age), min (age) FROM Sailors S GROUP BY S.rating SID SNAME RATING AGE 29 Brutus 1 33 85 Art 3 26 95 Bob 64 22 Dustin 7 45 Horatio 35 32 Lubber 8 56 Andy 74 9 58 Rusty 10 71 Zorba 16

GROUP BY Department SELECT S.rating, count(*), sum (age), max (age), min (age) FROM Sailors S WHERE S.rating > 7 GROUP BY S.rating

SELECT S.rating, count(*), sum (age), max (age), min (age) FROM Sailors S WHERE S.rating > 7 GROUP BY S.rating SID SNAME RATING AGE 22 Dustin 7 45 64 Horatio 35 32 Lubber 8 56 Andy 26 74 9 58 Rusty 10 71 Zorba 16

Queries With GROUP BY and HAVING SELECT [DISTINCT] target-list FROM relation-list WHERE qualification GROUP BY grouping-list HAVING group-qualification The target-list contains (i) attribute names (ii) terms with aggregate operations (e.g., MIN (S.age)). The attribute list (i) must be a subset of grouping-list. Intuitively, each answer tuple corresponds to a group, and these attributes must have a single value per group. (A group is a set of tuples that have the same value for all attributes in grouping-list.)

Conceptual Evaluation The cross-product of relation-list is computed, tuples that fail qualification are discarded, ‘unnecessary’ fields are deleted, and the remaining tuples are partitioned into groups by the value of attributes in grouping-list. The group-qualification is then applied to eliminate some groups. Expressions in group-qualification must have a single value per group! In effect, an attribute in group-qualification that is not an argument of an aggregate op also appears in grouping-list. (SQL does not exploit primary key semantics here!) One answer tuple is generated per qualifying group.

Queries With GROUP BY and HAVING SELECT S.rating, MIN (S.age) FROM Sailors S WHERE S.age >= 18 GROUP BY S.rating HAVING COUNT (*) > 1 Only S.rating and S.age are mentioned in the SELECT, GROUP BY or HAVING clauses; other attributes ‘unnecessary’. 2nd column of result is unnamed. (Use AS to name it.) Answer relation

Queries With GROUP BY For each red boat, find the number of reservations for this boat SELECT B.bid, COUNT (*) AS scount FROM Sailors S, Boats B, Reserves R WHERE S.sid=R.sid AND R.bid=B.bid AND B.color=‘red’ GROUP BY B.bid Grouping over a join of three relations. What do we get if we remove B.color=‘red’ from the WHERE clause and add a HAVING clause with this condition? What if we drop Sailors and the condition involving S.sid?

Queries With GROUP BY and HAVING Find the age of the youngest sailor with age > 18, for each rating with at least 2 sailors (of any age) SELECT S.rating, MIN (S.age) FROM Sailors S WHERE S.age > 18 GROUP BY S.rating HAVING 1 < (SELECT COUNT (*) FROM Sailors S2 WHERE S.rating=S2.rating) Shows HAVING clause can also contain a subquery. Compare this with the query where we considered only ratings with 2 sailors over 18! What if HAVING clause is replaced by: HAVING COUNT(*) >1

Queries With GROUP BY Aggregate operations cannot be nested! WRONG: SELECT S.rating FROM Sailors S WHERE S.age = (SELECT MIN (AVG (S2.age)) FROM Sailors S2) Correct solution (in SQL/92): SELECT Temp.rating, Temp.avgage FROM (SELECT S.rating, AVG (S.age) AS avgage FROM Sailors S GROUP BY S.rating) AS Temp WHERE Temp.avgage = (SELECT MIN (Temp.avgage) FROM Temp)

SELECT S.rating, count (*) FROM Sailors S WHERE S.rating > 7 GROUP BY S.rating HAVING count(*) >1 SID SNAME RATING AGE 22 Dustin 7 45 64 Horatio 35 32 Lubber 8 56 Andy 26 74 9 58 Rusty 10 71 Zorba 16

Null Values Field values in a tuple are sometimes unknown (e.g., a rating has not been assigned) or inapplicable (e.g., no spouse’s name). SQL provides a special value null for such situations. The presence of null complicates many issues. Is rating>8 true or false when rating is equal to null? What about AND, OR and NOT connectives? We need a 3-valued logic (true, false and unknown). Meaning of constructs must be defined carefully. (e.g., WHERE clause eliminates rows that don’t evaluate to true.) New operators (in particular, outer joins) possible/needed.

Summary SQL was an important factor in the early acceptance of the relational model; more natural than earlier, procedural query languages. Relationally complete; in fact, significantly more expressive power than relational algebra. Even queries that can be expressed in RA can often be expressed more naturally in SQL. Many alternative ways to write a query; optimizer should look for most efficient evaluation plan. In practice, users need to be aware of how queries are optimized and evaluated for best results.

Summary (Contd.) NULL for unknown field values brings many complications SQL allows specification of rich integrity constraints Triggers respond to changes in the database