1. 01-09-2007NOEA/IT FEN - Databases/SQL1 More about SQL Nested SELECT Other Joins Views Index

2. 01-09-2007NOEA/IT FEN - Databases/SQL2 SQL2 - DML (Q16): Sub queries (nested SELECTs) SELECTE.FNAME, E.LNAME FROMEMPLOYEE E WHEREE.SSNIN(SELECTESSN FROMDEPENDENT WHEREESSN = E.SSN ANDE.FNAME = DEPENDENT_NAME ANDSEX = E.SEX) Also ANY (SOME) and ALL in combination with comparison operators (>, >=, = and <>).

3. 01-09-2007NOEA/IT FEN - Databases/SQL3 SQL2 - DML ( Q16): Sub queries (nested SELECTs) SELECTE.FNAME, E.LNAME FROMEMPLOYEE E WHEREE.SSN IN(SELECTESSN FROMDEPENDENT WHEREESSN = E.SSN ANDE.FNAME = DEPENDENT_NAME ANDSEX = E.SEX) For each row in outer table (E), the inner SELECT is executed. If E.SSN is contained in the result of the inner SELECT, then E is included in the result table for the outer SELECT.

4. 01-09-2007NOEA/IT FEN - Databases/SQL4 SQL2 - DML (Q7): Existential quantifier - EXISTS: SELECTFNAME, LNAME FROMEMPLOYEE WHEREEXISTS (SELECT* FROMDEPENDENT WHERESSN = ESSN) AND EXISTS (SELECT* FROMDEPARTMENT WHERESSN = MGRSSN)

5. 01-09-2007NOEA/IT FEN - Databases/SQL5 SQL2 - DML (Q6): NOT EXISTS: SELECTFNAME, LNAME FROMEMPLOYEE WHERENOT EXISTS(SELECT* FROMDEPENDENT WHERESSN =ESSN)

6. 01-09-2007NOEA/IT FEN - Databases/SQL6 SQL2 - DML For All i SQL Although SQL is supposed to be an implementation of first order predicate logic, it does not support the universal qualifier (FORALL), only the existential quantifier (EXISTS) is supported. A well known (?) result from predicate logic can be used in a workaround: –Retrieving all elements satisfying some predicate is equivalent to retrieving elements that are not in the set of elements that do not satisfy the predicate: SELECT * FROM --- WHERE NOT EXISTS (SELECT * FROM --- WHERE NOT EXISTS --- -

7. 01-09-2007NOEA/IT FEN - Databases/SQL7 Let x be an arbitrary element in some set and p a predicate stating some condition on x: De Morgan’s Law:  (  x: p(x))   x:  p(x) Apply to  p(x):  (  x:  p(x))   x:  (  p(x)) Reduce the right hand side:  x: p(x)   (  x:  p(x)) “it is not true that there exists x, so p(x) is not true” – that is: “p is true for all x” SELECT * FROM --- WHERE NOT EXISTS (SELECT * FROM --- WHERE NOT EXISTS ---- A Side: Predicate Logic

8. 01-09-2007NOEA/IT FEN - Databases/SQL8 SQL2 - DML (Q3B): ”Retrieve the name of each employee who works on all projects controlled by department number 5” SELECTLNAME, FNAME FROMEMPLOYEE WHERENOT EXISTS (SELECT* FROMWORKS_ON B WHERE(B.PNO IN(SELECTPNUMBER FROMPROJECT WHEREDNUM = 5)) AND NOT EXISTS(SELECT* FROMWORKS_ON C WHEREC.ESSN = SSN AND C.PNO=B.PNO))

9. 01-09-2007NOEA/IT FEN - Databases/SQL9 SQL2 – DML: SELECT Queries: SELECT FROM [WHERE ] [GROUP BY ] [HAVING ] [ORDER BY ] [...]:WHERE, GROUP BY, HAVING and ORDER BY may be omitted.

10. 01-09-2007NOEA/IT FEN - Databases/SQL10 SQL2 - DML SELECT DISTINCTESSN FROMWORKS_ON WHEREPNO IN (1,2,3) SELECTFNAME, LNAME FROMEMPLOYEE WHERESUPERSSN IS NULL

11. 01-09-2007NOEA/IT FEN - Databases/SQL11 SQL2 - DML SELECTE.LNAME AS EMP_NAME, S.LNAME AS SUPER_NAME FROMEMPLOYEE AS E, EMPLOYEE AS S WHEREE.SUPERSSN = S.SSN New coulomb names in the resulting table. AS may be omitted in FROM part.

12. 01-09-2007NOEA/IT FEN - Databases/SQL12 SQL2 - DML Alternative notations for join: SELECTFNAME, LNAME, ADDRESS FROM(EMPLOYEE JOIN DEPARTMENT ON DNO=DNUMBER) WHEREDNAME = ’Research’ Provides a more clear syntax and opens for more specialised joins.

13. 01-09-2007NOEA/IT FEN - Databases/SQL13 SQL2 - DML Natural join (not MS SQL Server): (Q1B): SELECT FNAME, LNAME, ADDRESS FROM (EMPLOYEE NATURAL JOIN (DEPARTMENT AS DEPT (DNAME,DNO,MSSN,MSDATE))) WHERE DNAME = ’Research’ DEPARTMENT.DNUMBER must be rename to DNO in order to match EMPLOYEE.DNO. Natural join is over two attributes with the same name (EMPLOYEE.DNO = DEPT.DNO).

14. 01-09-2007NOEA/IT FEN - Databases/SQL14 SQL2 - DML Outer join: SELECTE.LNAME AS EMP_NAME, S.LNAME AS SUPER_NAME FROMEMPLOYEE AS E, EMPLOYEE AS S WHEREE.SUPERSSN = S.SSN Retrieves only employees who have a supervisor. Left Outer Join retrieves all employees and inserts NULL in the S- attributes for employees with no supervisor. SELECTE.LNAME AS EMP_NAME, S.LNAME AS SUPER_NAME FROM(EMPLOYEE E LEFT OUTER JOIN EMPLOYEE S ON E.SUPERSSN = S.SSN) Also RIGTH OUTER JOIN and FULL OUTER JOIN.

15. 01-09-2007NOEA/IT FEN - Databases/SQL15 SQL2 - DML

16. 01-09-2007NOEA/IT FEN - Databases/SQL16 What about employees with no supervisor?

17. 01-09-2007NOEA/IT FEN - Databases/SQL17 Here they are!

18. 01-09-2007NOEA/IT FEN - Databases/SQL18 SQL2 - DML

19. 01-09-2007NOEA/IT FEN - Databases/SQL19 SQL2 - DML

20. 01-09-2007NOEA/IT FEN - Databases/SQL20 SQL2 - DML Also: –CROSS JOIN (Cartesian Product) –UNION JOIN SQL2 provides many different ways of expressing the same join: –This can be view as an advantage: More simple expressions –Or as an disadvantage: More complicated language

21. 01-09-2007NOEA/IT FEN - Databases/SQL21 SQL2 - DML Aggregate Functions: –COUNT –SUM –MAX –MIN –AVG

22. 01-09-2007NOEA/IT FEN - Databases/SQL22 SQL2 - DML Ex.: ”Number of Employees in the research department” SELECTCOUNT(*) FROMEMPLOYEE, DEPARTMENT WHEREDNO = DNUMBER AND DNAME = ’Research’

23. 01-09-2007NOEA/IT FEN - Databases/SQL23 SQL2 - DML (Q24)

24. 01-09-2007NOEA/IT FEN - Databases/SQL24 Result of Q24

25. 01-09-2007NOEA/IT FEN - Databases/SQL25 SQL2 - DML (Q26)

26. 01-09-2007NOEA/IT FEN - Databases/SQL26 Result of Q26, 1

27. 01-09-2007NOEA/IT FEN - Databases/SQL27 Result of Q26, 2

28. 01-09-2007NOEA/IT FEN - Databases/SQL28 SQL2 - DML

29. 01-09-2007NOEA/IT FEN - Databases/SQL29 SQL - VIEWS A view is virtual table which is created from one or more existing base tables. Views may be used in a layered architecture to provide different view of the database to different users. May also be used to increase efficiency of frequent queries, for instance to avoid JOINs.

30. 01-09-2007NOEA/IT FEN - Databases/SQL30 SQL - VIEWS CREATE VIEWWORKS_ON1 AS SELECTFNAME, LNAME, PNAME, HOURS FROMEMPLOYEE, PROJECT, WORKS_ON WHERESSN=ESSN AND PNO=PNUMBER; Using this view, the query: SELECTFNAME, LNAME, PNAME FROMEMPLOYEE, PROJECT, WORKS_ON WHEREPNAME = 'ProductX' AND SSN = ESSN AND PNO = PNUMBER; May written as SELECTFNAME, LNAME, PNAME FROMWORKS_ON1 WHEREPNAME = 'ProductX'; And hence saving the join

31. 01-09-2007NOEA/IT FEN - Databases/SQL31 SQL - VIEWS Updating through views is problematic: FX: Transfer John Smith from the project 'ProductX' to the project 'ProductY’ UPDATEWORKS_ON1 SETPNAME = ’ProductY’ WHERELNAME = ’Smith’ ANDFNAME = ’John’ ANDPNAME = ’ProductX’

32. 01-09-2007NOEA/IT FEN - Databases/SQL32 SQL - VIEWS Which update of the base tables should be executed? This? Or this?

33. 01-09-2007NOEA/IT FEN - Databases/SQL33 SQL - VIEWS Views and update: Updatable views Gray zone Not updatable views

34. 01-09-2007NOEA/IT FEN - Databases/SQL34 SQL - VIEWS Generally: Views defined over one base table can be updated, if the primary key (ore some candidate key) is included in the view. Views defined by joining more base tables are generally not updatable. Some joined view are in principle updatable: all primary keys from the base tables must be included in the view. Views defined using aggregate or grouping functions are not updatable. SQL2 standard establishes that joined view are not updatable.

35. 01-09-2007NOEA/IT FEN - Databases/SQL35 Index Index is often considered part of the DDL of SQL –index is about internal physical storage access, and –as such NOT a part of the SQL2 standard –many SQL versions include index anyway Previous versions of SQL includes a CREATE INDEX statement –Is used for speeding up queries, for instance: CREATE INDEX LNAME_INDEXON EMPLOYEE(LNAME); –Index is in some older SQL implementations also used to simulate primary keys: CREATE UNIQUE INDEX SSN_INDEX ON EMPLOYEE(SSN);

36. 01-09-2007NOEA/IT FEN - Databases/SQL36 Index –Often it is possible to define one (and only one) clustering index: CREATE INDEX DNO_INDEX ONEMPLOYEE(DNO) CLUSTER; –The effect is that employees in the same department are stored physically close –Hereby queries concerning employees in the same department are speeded up. Why is that?

37. 01-09-2007NOEA/IT FEN - Databases/SQL37 Databaser (SQL) og programudviklingsværktøjer ODBC/JDBC giver standardiseret tilgang til RDBMS

38. 01-09-2007NOEA/IT FEN - Databases/SQL38 Databaseprogrammering fra 3GLs og OOPLs SQL og typiske programmeringssprog som Java, C, Cobol etc. er ikke ”kompatible”: Impedans-mismatch: –Programmeringssprogets datatyper er ikke afstemt med databasens domæner –SQL er mængde- (tabel-) orienteret: alle resultater er en tabel med et antal tupler. 3GLs og OOPLs er tuple- (objekt-)orienteret, dvs. der er behov for en datastruktur i programmeringssproget

39. 01-09-2007NOEA/IT FEN - Databases/SQL39 Embedded SQL Databaseaccess vha. SQL fra 3GL/OOPL (værtssprog): Er baseret Cursor-begrebet: En cursor kan opfattes som en pointer, der udpeger aktiv række i tabellen, som SQL-sætningen resulterer i En cursor er nødvendig, når resultatet af en SQL-sætning er mere end een tuple (værtssproget er record- (objekt-) orienteret) Er leverandørafhængig Visse moderne værktøjer (fx Visual Studio.NET) kan tilsyneladende returnere en mængde af forekomster (dataset eller ResultSet, men reelt er der tale om en indpakket cursor ODBC (Open Data Base Connectivity): Resultset svarer til en cursor. I OOPLs kaldes en cursor ofte en iterator (Enumerator i C#).