Cs3431 SQL: Updates (DML) and Views (DDL). cs3431 SQL DML (Updating the Data) Insert Delete Update.

Slides:



Advertisements
Similar presentations
TURKISH STATISTICAL INSTITUTE 1 /34 SQL FUNDEMANTALS (Muscat, Oman)
Advertisements

Basic SQL Introduction Presented by: Madhuri Bhogadi.
Relational Database. Relational database: a set of relations Relation: made up of 2 parts: − Schema : specifies the name of relations, plus name and type.
Relational Databases Chapter 4.
Murali Mani Normalization. Murali Mani What and Why Normalization? To remove potential redundancy in design Redundancy causes several anomalies: insert,
Chapter 3 The Relational Model Transparencies © Pearson Education Limited 1995, 2005.
VIEWS Pertemuan 7 Matakuliah: T0413/Current Popular IT II Tahun: 2007.
Dec 4, 2003Murali Mani SQL B term 2004: lecture 14.
Murali Mani The Relational Model. Murali Mani Why Relational Model? Currently the most widely used Vendors: Oracle, Microsoft, IBM Older models still.
Murali Mani SQL: Updates (DML) and Views (DDL). Murali Mani SQL DML (Updating the Data) Insert Delete Update.
Chapter 3. 2 Chapter 3 - Objectives Terminology of relational model. Terminology of relational model. How tables are used to represent data. How tables.
Nov 24, 2003Murali Mani SQL B term 2004: lecture 12.
CS3431 SQL : Query Language. CS3431 SELECT-FROM-WHERE SELECT * FROM Student WHERE sName=“Greg” AND address=“320 FL”  (sName=“Greg” AND address=“320 FL”)
Murali Mani SQL. Murali Mani SELECT-FROM-WHERE SELECT * FROM Student WHERE sName=“Greg” AND address=“320 FL”  (sName=“Greg” AND address=“320 FL”) (Student)
Cs3431 Normalization. cs3431 Why Normalization? To remove potential redundancy in design Redundancy causes several anomalies: insert, delete and update.
Dec 15, 2003Murali Mani Transactions and Security B term 2004: lecture 17.
Cs3431 Transactions, Logging and Security. cs3431 Transactions: What and Why? A set of operations on a database must appear as one “unit”. Example: Consider.
Database Systems More SQL Database Design -- More SQL1.
View and Materialized view. What is a view? Logically represents subset of data from one or more table. In sql, a view is a virtual relation based on.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Lecture 2 The Relational Model. Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical relations.
Chapter 4 The Relational Model Pearson Education © 2014.
Chapter 4 The Relational Model.
The Relational Model. Review Why use a DBMS? OS provides RAM and disk.
Views: Limiting Access to Data A view is a named select statement that is stored in a database as an object. It allows you to view a subset of rows or.
Chapter 10 Views. Topics in this Chapter What are Views For? View Retrievals View Updates Snapshots SQL Facilities.
Quick review of SQL And conversion to Oracle SQL.
Views Lesson 7.
Constraints, Triggers and Views COMSATS INSTITUTE OF INFORMATION TECHNOLOGY, VEHARI.
Chapter 2 Views. Objectives ◦ Create simple and complex views ◦ Creating a view with a check constraint ◦ Retrieve data from views ◦ Data manipulation.
CIS 375—Web App Dev II SQL. 2 Introduction SQL (Structured _______ Language) is an ANSI standard language for accessing databases.ANSI SQL can execute.
DATABASE VIEWS CHAPTER 5 (6/E) CHAPTER 8 (5/E) 1.
IS 230Lecture 6Slide 1 Lecture 7 Advanced SQL Introduction to Database Systems IS 230 This is the instructor’s notes and student has to read the textbook.
Dec 8, 2003Murali Mani Constraints B term 2004: lecture 15.
CIS 375—Web App Dev II SQL. 2 Introduction SQL (Structured _______ Language) is an ANSI standard language for accessing databases.ANSI SQL can execute.
SQL Jan 20,2014. DBMS Stores data as records, tables etc. Accepts data and stores that data for later use Uses query languages for searching, sorting,
CMPT 258 Database Systems The Relationship Model PartII (Chapter 3)
Lecture 3 Book Chapter 3 (part 2 ) From ER to Relational.
Chapter 5 : Integrity And Security  Domain Constraints  Referential Integrity  Security  Triggers  Authorization  Authorization in SQL  Views 
The Relational Model. 2 Relational Model Terminology u A relation is a table with columns and rows. –Only applies to logical structure of the database,
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 5 SQL.
CS34311 The Relational Model. cs34312 Why Relational Model? Currently the most widely used Vendors: Oracle, Microsoft, IBM Older models still used IBM’s.
Manipulating Data Lesson 3. Objectives Queries The SELECT query to retrieve or extract data from one table, how to retrieve or extract data by using.
The Relational Model © Pearson Education Limited 1995, 2005 Bayu Adhi Tama, M.T.I.
1 CS 430 Database Theory Winter 2005 Lecture 13: SQL DML - Modifying Data.
SQL: Structured Query Language Instructor: Mohamed Eltabakh 1 Part II.
7 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel 7.6 Advanced Select Queries SQL provides useful functions that.
Constraints and Views Chap. 3-5 continued (7 th ed. 5-7)
SQL: Interactive Queries (2) Prof. Weining Zhang Cs.utsa.edu.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 The Relational Model Chapter 3.
SQL: Structured Query Language Instructor: Mohamed Eltabakh 1.
More SQL: Complex Queries, Triggers, Views, and Schema Modification
Prepared by : Moshira M. Ali CS490 Coordinator Arab Open University
SQL : Query Language Part II CS3431.
SQL Views CS542.
SQL : Query Language CS3431.
Normalization Murali Mani.
SQL Views and Updates cs3431.
Advanced SQL: Views & Triggers
Chapter 2 Views.
More SQL: Complex Queries, Triggers, Views, and Schema Modification
SQL: Structured Query Language
Instructor: Mohamed Eltabakh
Chapter 2 Views.
Normalization cs3431.
SQL: Structured Query Language
SQL: Structured Query Language
SQL: Structured Query Language
SQL: Structured Query Language
Presentation transcript:

cs3431 SQL: Updates (DML) and Views (DDL)

cs3431 SQL DML (Updating the Data) Insert Delete Update

cs3431 Inserting tuples INSERT INTO Student VALUES (6, ‘Emily’, ‘324 FL’, NULL); INSERT INTO Student (sNumber, sName) VALUES (6, ‘Emily’); INSERT INTO Professor (pNumber) SELECT professor FROM Student;

cs3431 Delete and Update Deleting tuples DELETE FROM Student WHERE sNumber=‘6’; Updating tuples UPDATE Student SET professor=‘ER’ WHERE sNumber=‘6’

cs3431 Views NOTE: You can present logical subsets or combinations of the data by creating views of tables. A view is a virtual table based on a table or another view. A view contains no data of its own but is like a window through which data from tables can be viewed or changed. The tables on which a view is based are called base tables. The view is stored as a SELECT statement in the data dictionary.

cs3431 Views View is a virtual relation defined by: Named stored SQL query Views can be queried like any “base” relation.

cs3431 Views CREATE VIEW as CREATE VIEW studentProfessor (student, professor) AS SELECT sName, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; DROP VIEW studentProfessor

cs3431 Views - Example sNumbersNameaddressprofessor 1Dave320FL1 2Greg320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor CREATE VIEW studentProfessor (student, professor) AS SELECT sName, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; SELECT * from studentProfessor studentprofessor DaveMM GregMM MattER

cs3431 Views - Example sNumbersNameaddressprofessor 1Dave320FL1 2Greg320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor CREATE VIEW studentProfessor (student, professor) AS SELECT sName, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; SELECT professor, count(*) FROM studentProfessor GROUPBY professor; studentprofessor DaveMM GregMM MattER

cs3431 Querying Views CREATE VIEW studentProfessor (student, professor) AS SELECT sName, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; SELECT pnumber as professor, count(*) FROM Student, Professor WHERE Student.professor = Professor.pNumber GROUPBY professor; studentprofessor DaveMM GregMM MattER SELECT professor, count(*) FROM studentProfessor GROUPBY professor;

cs3431 Views ? Why ? View is a virtual relation ? Convenience: Queries on base relations might be “complex” Logical Data Independence: “Base tables” may change, but still queries using views need not change. Customization: Provide different views of the same data. Security: Expose only necessary data to users

cs3431 Updating Views Consider views defined with only one relation in the FROM clause such as: CREATE VIEW MyStudent (num, name) AS SELECT sNumber, sName FROM Student; Question: Are these views are updatable? Answer: Updating these views are done by updating the underlying Student tables.

cs3431 Updating Single Relation Views DELETE FROM MyStudent WHERE name=`Dave'; -- This will delete the corresponding row from the Student table DELETE FROM Student WHERE name=`Dave'; The update is valid !

cs3431 Updating Single Relation Views INSERT INTO MyStudent VALUES (4, `Mary’); -- This will be translated to: INSERT INTO Student (sNumber, sName) VALUES (4, `Mary’);

cs3431 Inserting into single relation views CREATE VIEW MyStudent1(name) AS SELECT sName FROM Student; INSERT INTO MyStudent1 VALUES (‘Mary’) will be translated to: INSERT INTO Student(sName) VALUES (‘Mary’). This will return an error as sNumber must not be null.

cs3431 Updating Single Relation views If the SELECT clause specifies DISTINCT, then the view is not updatable. For instance, the following view is not updatable. CREATE VIEW MyStudent2(num) AS SELECT DISTINCT sNumber FROM Student;

cs3431 Updating Single Relation Views WHERE clause may specify subqueries. CREATE VIEW MyStudent3 (num, name) AS SELECT sNumber, sName FROM Student WHERE sNumber NOT IN (SELECT sNumber FROM Student); -- this view will always have 0 tuples. -- Insert into this view will still insert into student table, though that tuple does not appear in the view.

cs3431 Multiple relation views: Delete Consider a multi-relation view such as CREATE VIEW studentProf (studentname, profname) AS SELECT sName, pName FROM Student, Professor WHERE SName = PName; -- Ambigious what base table to update ? -- Side effects of other tuples disappear out of the view.

cs3431 Multiple relation views Consider a multi-relation view such as CREATE VIEW studentProf (studentname, profname) AS SELECT sName, pName FROM Student, Professor WHERE SName = PName; sNumbersNameaddressprofessor 1MM320FL1 2MM320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor

cs3431 Multi-Relation View Deletes can be done against multi-relation views if there is a table such that the view and the table have the same key.

cs3431 Views - Example sNumbersNameaddressprofessor 1Dave320FL1 2Greg320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor CREATE VIEW studentProfessor (student, professor) AS SELECT sNumber, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; studentprofessor 1MM 2 3ER 1.pNumber is key in Professor 2.sNumber is key of Student 3.sNumber is key of view

cs3431 Deleting from multi-relation views Try the following update statements: DELETE FROM studentProfessor WHERE professor='MM'; -- What will be deleted ?

cs3431 Views - Example sNumbersNameaddressprofessor 1Dave320FL1 2Greg320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor CREATE VIEW studentProfessor (student, professor) AS SELECT sNumber, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; studentprofessor 1MM 2 3ER DELETE FROM studentProfessor WHERE professor='MM'; -- This will actually delete the two rows in the student table.

cs3431 Views - Example sNumbersNameaddressprofessor 1Dave320FL1 2Greg320FL1 3Matt320FL2 Student pNumberpNameaddress 1MM235FL 2ER241FL Professor CREATE VIEW studentProfessor (student, professor) AS SELECT sNumber, pName FROM Student, Professor WHERE Student.professor = Professor.pNumber; Suppose we drop key constraint on the professor table for this view. Now delete will fail because there is no table whose key is the key of the view.

cs3431 Inserting into multi-relation views Consider view definition: CREATE VIEW studentProf(student, professor) AS SELECT sNumber, pName FROM Student, Professor WHERE professor=pNumber; INSERT INTO Studentprof VALUES (4, 'ER'); -- THIS ABOVE INSERT WILL FAIL AS IT TRIES TO INSERT INTO Professor TABLE AS WELL. INSERT INTO Studentprof(student) VALUES (4); -- THIS ABOVE INSERT WILL SUCCEED.

cs3431 Inserting into multi-relation views Insert will succeed only if The insert translates to insert into only one table. The key for the table to be inserted will also be a key for the view.

cs3431 Views - Summary Views are useful – Virtual relations Querying through views is always possible Updating through views has limitations