1. Advanced SQL Lecture 4

2. 2 Advanced SQL Advanced SQL SQL Data Types and Schemas Integrity Constraints Authorization Embedded SQL Dynamic SQL Functions and Procedural Constructs Recursive Queries Advanced SQL Features

3. 3 Built-in Data Types in SQL date: Dates, containing a (4 digit) year, month and date  Example: date ‘2005-7-27’ time: Time of day, in hours, minutes and seconds.  Example: time ‘09:00:30’ time ‘09:00:30.75’ timestamp: date plus time of day  Example: timestamp ‘2005-7-27 09:00:30.75’ interval: period of time  Example: interval ‘1’ day  Subtracting a date/time/timestamp value from another gives an interval value  Interval values can be added to date/time/timestamp values

4. 4 Build-in Data Types in SQL Can extract values of individual fields from date/time/timestamp  Example: extract (year from r.starttime) Can cast string types to date/time/timestamp  Example: cast as date  Example: cast as time

5. 5 User-Defined Types create type construct in SQL creates user-defined type create type Dollars as numeric (12,2) final create domain construct in SQL-92 creates user-defined domain types create domain person_name char(20) not null Types and domains are similar. Domains can have constraints, such as not null, specified on them.

6. 6 Domain Constraints Domain constraints are the most elementary form of integrity constraint. They test values inserted in the database, and test queries to ensure that the comparisons make sense. New domains can be created from existing data types  Example:create domain Dollars numeric(12, 2) create domain Pounds numeric(12,2) We cannot assign or compare a value of type Dollars to a value of type Pounds.  However, we can convert type as below (cast r.A as Pounds) (Should also multiply by the dollar-to-pound conversion-rate)

7. 7 Large-Object Types Large objects (photos, videos, CAD files, etc.) are stored as a large object:  blob: binary large object -- object is a large collection of uninterpreted binary data (whose interpretation is left to an application outside of the database system)  clob: character large object -- object is a large collection of character data  When a query returns a large object, a pointer is returned rather than the large object itself.

8. 8 Integrity Constraints Integrity constraints guard against accidental damage to the database, by ensuring that authorized changes to the database do not result in a loss of data consistency.  A checking account must have a balance greater than $10,000.00  A salary of a bank employee must be at least $4.00 an hour  A customer must have a (non-null) phone number

9. 9 Constraints on a Single Relation Constraints on a Single Relation not null primary key unique check (P ), where P is a predicate

10. 10 Not Null Constraint Declare branch_name for branch is not null branch_name char(15) not null Declare the domain Dollars to be not null create domain Dollars numeric(12,2) not null

11. 11 The Unique Constraint unique ( A 1, A 2, …, A m ) The unique specification states that the attributes A 1, A 2, … A m Form a candidate key. Candidate keys are permitted to be null (in contrast to primary keys).

12. 12 The check clause check (P ), where P is a predicate Example: Declare branch_name as the primary key for branch and ensure that the values of assets are non- negative. create table branch (branch_name char(15), branch_city char(30), assets integer, primary key (branch_name), check (assets >= 0))

13. 13 The check clause The check clause in SQL-92 permits domains to be restricted:  Use check clause to ensure that an hourly_wage domain allows only values greater than a specified value. create domain hourly_wage numeric(5,2) constraint value_test check(value > = 4.00)  The domain has a constraint that ensures that the hourly_wage is greater than 4.00  The clause constraint value_test is optional; useful to indicate which constraint an update violated.

14. 14 Referential Integrity Ensures that a value that appears in one relation for a given set of attributes also appears for a certain set of attributes in another relation.  Example: If “Perryridge” is a branch name appearing in one of the tuples in the account relation, then there exists a tuple in the branch relation for branch “Perryridge”. Formal Definition  Let r 1 (R 1 ) and r 2 (R 2 ) be relations with primary keys K 1 and K 2 respectively.  The subset  of R 2 is a foreign key referencing K 1 in relation r 1, if for every t 2 in r 2 there must be a tuple t 1 in r 1 such that t 1 [K 1 ] = t 2 [  ].  Referential integrity constraint also called subset dependency since its can be written as   (r 2 )   K1 (r 1 )

15. 15 Checking Referential Integrity on Database Modification The following tests must be made in order to preserve the following referential integrity constraint:   (r 2 )   K (r 1 ) Insert. If a tuple t 2 is inserted into r 2, the system must ensure that there is a tuple t 1 in r 1 such that t 1 [K] = t 2 [  ]. That is t 2 [  ]   K (r 1 ) Delete. If a tuple, t 1 is deleted from r 1, the system must compute the set of tuples in r 2 that reference t 1 :   = t 1 [K] (r 2 ) If this set is not empty  either the delete command is rejected as an error, or  the tuples that reference t 1 must themselves be deleted (cascading deletions are possible).

16. 16 Referential Integrity in SQL Primary and candidate keys and foreign keys can be specified as part of the SQL create table statement:  The primary key clause lists attributes that comprise the primary key.  The unique key clause lists attributes that comprise a candidate key.  The foreign key clause lists the attributes that comprise the foreign key and the name of the relation referenced by the foreign key. By default, a foreign key references the primary key attributes of the referenced table foreign key (account-number) references account Short form for specifying a single column as foreign key account-number char (10) references account Reference columns in the referenced table can be explicitly specified  but must be declared as primary/candidate keys foreign key (account-number) references account(account-number)

17. 17 Referential Integrity in SQL Alternative to cascading:  on delete set null  on delete set default Null values in foreign key attributes complicate SQL referential integrity semantics, and are best prevented using not null  if any attribute of a foreign key is null, the tuple is defined to satisfy the foreign key constraint!

18. 18 Referential Integrity in SQL – Example create table customer (customer_namechar(20), customer_streetchar(30), customer_citychar(30), primary key (customer_name )) create table branch (branch_namechar(15), branch_citychar(30), assetsnumeric(12,2), primary key (branch_name ))

19. 19 Referential Integrity in SQL – Example create table account (account_numberchar(10), branch_namechar(15), balanceinteger, primary key (account_number), foreign key (branch_name) references branch ) create table depositor (customer_namechar(20), account_numberchar(10), primary key (customer_name, account_number), foreign key (account_number ) references account, foreign key (customer_name ) references customer )

20. 20 Cascading Actions in SQL create table account... foreign key(branch-name) references branch on delete cascade on update cascade... ) Due to the on delete cascade clauses, if a delete of a tuple in branch results in referential-integrity constraint violation, the delete “cascades” to the account relation, deleting the tuple that refers to the branch that was deleted. Cascading updates are similar.

21. 21 Cascading Actions in SQL (Cont.) If there is a chain of foreign-key dependencies across multiple relations, with on delete cascade specified for each dependency, a deletion or update at one end of the chain can propagate across the entire chain. If a cascading update to delete causes a constraint violation that cannot be handled by a further cascading operation, the system aborts the transaction.  As a result, all the changes caused by the transaction and its cascading actions are undone. Referential integrity is only checked at the end of a transaction  Intermediate steps are allowed to violate referential integrity provided later steps remove the violation  Otherwise it would be impossible to create some database states, e.g. insert two tuples whose foreign keys point to each other  E.g. spouse attribute of relation marriedperson(name, address, spouse)

22. 22 Assertions An assertion is a predicate expressing a condition that we wish the database always to satisfy. An assertion in SQL takes the form create assertion check When an assertion is made, the system tests it for validity, and tests it again on every update that may violate the assertion  This testing may introduce a significant amount of overhead; hence assertions should be used with great care. Asserting for all X, P(X) is achieved in a round-about fashion using not exists X such that not P(X)

23. 23 Assertion Example Every loan has at least one borrower who maintains an account with a minimum balance or $1000.00 create assertion balance_constraint check (not exists ( select * from loan where not exists ( select * from borrower, depositor, account where loan.loan_number = borrower.loan_number and borrower.customer_name = depositor.customer_name and depositor.account_number = account.account_number and account.balance >= 1000)))

24. 24 Assertion Example The sum of all loan amounts for each branch must be less than the sum of all account balances at the branch. create assertion sum_constraint check (not exists (select * from branch where (select sum(amount ) from loan where loan.branch_name = branch.branch_name ) >= (select sum (amount ) from account where loan.branch_name = branch.branch_name )))

25. 25 Triggers A trigger is a statement that is executed automatically by the system as a side effect of a modification to the database. To design a trigger mechanism, we must:  Specify the conditions under which the trigger is to be executed.  Specify the actions to be taken when the trigger executes. Triggers introduced to SQL standard in SQL:1999, but supported even earlier using non-standard syntax by most databases.

26. 26 Trigger Example Suppose that instead of allowing negative account balances, the bank deals with overdrafts by  setting the account balance to zero  creating a loan in the amount of the overdraft  giving this loan a loan number identical to the account number of the overdrawn account The condition for executing the trigger is an update to the account relation that results in a negative balance value.

27. 27 Trigger Example in SQL:1999 create trigger overdraft-trigger after update on account referencing new row as nrow for each row when nrow.balance < 0 begin atomic insert into borrower (select customer-name, account-number from depositor where nrow.account-number = depositor.account-number); insert into loan values (n.row.account-number, nrow.branch-name, – nrow.balance); update account set balance = 0 where account.account-number = nrow.account-number end

28. 28 Triggering Events and Actions in SQL Triggering event can be insert, delete or update Triggers on update can be restricted to specific attributes  E.g. create trigger overdraft-trigger after update of balance on account Values of attributes before and after an update can be referenced  referencing old row as : for deletes and updates  referencing new row as : for inserts and updates Triggers can be activated before an event, which can serve as extra constraints. E.g. convert blanks to null. create trigger setnull-trigger before update on r referencing new row as nrow for each row when nrow.phone-number = ‘ ‘ set nrow.phone-number = null

29. 29 Statement Level Triggers Instead of executing a separate action for each affected row, a single action can be executed for all rows affected by a transaction  Use for each statement instead of for each row  Use referencing old table or referencing new table to refer to temporary tables (called transition tables) containing the affected rows  Can be more efficient when dealing with SQL statements that update a large number of rows

30. 30 External World Actions We sometimes require external world actions to be triggered on a database update  E.g. re-ordering an item whose quantity in a warehouse has become small, or turning on an alarm light, Triggers cannot be used to directly implement external-world actions, BUT  Triggers can be used to record actions-to-be-taken in a separate table  Have an external process that repeatedly scans the table, carries out external-world actions and deletes action from table E.g. Suppose a warehouse has the following tables  inventory(item, level): How much of each item is in the warehouse  minlevel(item, level) : What is the minimum desired level of each item  reorder(item, amount): What quantity should we re-order at a time  orders(item, amount) : Orders to be placed (read by external process)

31. 31 External World Actions create trigger reorder-trigger after update of amount on inventory referencing old row as orow, new row as nrow for each row when nrow.level < = (select level from minlevel where minlevel.item = orow.item) and orow.level > (select level from minlevel where minlevel.item = orow.item) begin insert into orders (select item, amount from reorder where reorder.item = orow.item) end

32. 32 Triggers in MS-SQLServer Syntax create trigger overdraft-trigger on account for update as if inserted.balance < 0 begin insert into borrower (select customer-name,account-number from depositor, inserted where inserted.account-number = depositor.account-number) insert into loan values (inserted.account-number, inserted.branch-name, – inserted.balance) update account set balance = 0 from account, inserted where account.account-number = inserted.account-number end

33. 33 When Not To Use Triggers Triggers were used earlier for tasks such as  maintaining summary data (e.g. total salary of each department)  Replicating databases by recording changes to special relations (called change or delta relations) and having a separate process that applies the changes over to a replica There are better ways of doing these now:  Databases today provide built in materialized view facilities to maintain summary data  Databases provide built-in support for replication Encapsulation facilities can be used instead of triggers in many cases  Define methods to update fields  Carry out actions as part of the update methods instead of through a trigger

34. 34 Security Security - protection from malicious attempts to steal or modify data.  Database system level  Authentication and authorization mechanisms to allow specific users access only to required data  We concentrate on authorization in the rest of this chapter  Operating system level  Operating system super-users can do anything they want to the database! Good operating system level security is required.  Network level: must use encryption to prevent  Eavesdropping (unauthorized reading of messages)  Masquerading (pretending to be an authorized user or sending messages supposedly from authorized users)

35. 35 Physical Level Security Protection of equipment from floods, power failure, etc. Protection of disks from theft, erasure, physical damage, etc. Protection of network and terminal cables from wiretaps non- invasive electronic eavesdropping, physical damage, etc. Solutions: Replicated hardware:  mirrored disks, dual busses, etc.  multiple access paths between every pair of devises Physical security: locks,police, etc. Software techniques to detect physical security breaches.

36. 36 Human Level Security Protection from stolen passwords, sabotage, etc. Primarily a management problem:  Frequent change of passwords  Use of “non-guessable” passwords  Log all invalid access attempts  Data audits  Careful hiring practices

37. 37 Operating System Level Security Protection from invalid logins File-level access protection (often not very helpful for database security) Protection from improper use of “superuser” authority. Protection from improper use of privileged machine intructions.

38. 38 Network-Level Security Each site must ensure that it communicate with trusted sites (not intruders). Links must be protected from theft or modification of messages Mechanisms:  Identification protocol (password-based),  Cryptography.

39. 39 Database-Level Security Assume security at network, operating system, human, and physical levels. Database specific issues:  each user may have authority to read only part of the data and to write only part of the data.  User authority may correspond to entire files or relations, but it may also correspond only to parts of files or relations. Local autonomy suggests site-level authorization control in a distributed database. Global control suggests centralized control.

40. 40 Authorization Forms of authorization on parts of the database: Read - allows reading, but not modification of data. Insert - allows insertion of new data, but not modification of existing data. Update - allows modification, but not deletion of data. Delete - allows deletion of data. Forms of authorization to modify the database schema (covered in Chapter 8): Index - allows creation and deletion of indices. Resources - allows creation of new relations. Alteration - allows addition or deletion of attributes in a relation. Drop - allows deletion of relations.

41. 41 Authorization Specification in SQL The grant statement is used to confer authorization grant on to is:  a user-id  public, which allows all valid users the privilege granted  A role (more on this in Chapter 8) Granting a privilege on a view does not imply granting any privileges on the underlying relations. The grantor of the privilege must already hold the privilege on the specified item (or be the database administrator).

42. 42 Embedded SQL The SQL standard defines embeddings of SQL in a variety of programming languages such as C, Java, and Cobol. A language to which SQL queries are embedded is referred to as a host language, and the SQL structures permitted in the host language comprise embedded SQL. The basic form of these languages follows that of the System R embedding of SQL into PL/I. EXEC SQL statement is used to identify embedded SQL request to the preprocessor EXEC SQL END_EXEC Note: this varies by language (for example, the Java embedding uses # SQL { …. }; )

43. 43 Embedded SQL The open statement causes the query to be evaluated EXEC SQL open c END_EXEC The fetch statement causes the values of one tuple in the query result to be placed on host language variables. EXEC SQL fetch c into :cn, :cc END_EXEC Repeated calls to fetch get successive tuples in the query result A variable called SQLSTATE in the SQL communication area (SQLCA) gets set to ‘02000’ to indicate no more data is available The close statement causes the database system to delete the temporary relation that holds the result of the query. EXEC SQL close c END_EXEC Note: above details vary with language. For example, the Java embedding defines Java iterators to step through result tuples.

44. 44 Updates Through Cursors Can update tuples fetched by cursor by declaring that the cursor is for update declare c cursor for select * from account where branch_name = ‘Perryridge’ for update To update tuple at the current location of cursor c update account set balance = balance + 100 where current of c

45. 45 Example Query Specify the query in SQL and declare a cursor for it EXEC SQL declare c cursor for select customer_name, customer_city from depositor, customer, account where depositor.customer_name = customer.customer_name and depositor account_number = account.account_number and account.balance > :amount END_EXEC From within a host language, find the names and cities of customers with more than the variable amount dollars in some account.

46. 46 Dynamic SQL Allows programs to construct and submit SQL queries at run time. Example of the use of dynamic SQL from within a C program. char * sqlprog = “update account set balance = balance * 1.05 where account_number = ?” EXEC SQL prepare dynprog from :sqlprog; char account [10] = “A-101”; EXEC SQL execute dynprog using :account; The dynamic SQL program contains a ?, which is a place holder for a value that is provided when the SQL program is executed.

47. 47 Procedural Extensions and Stored Procedures SQL provides a module language  Permits definition of procedures in SQL, with if-then-else statements, for and while loops, etc.  more in Chapter 9 Stored Procedures  Can store procedures in the database  then execute them using the call statement  permit external applications to operate on the database without knowing about internal details

48. 48 SQL Functions Define a function that, given the name of a customer, returns the count of the number of accounts owned by the customer. create function account_count (customer_name varchar(20)) returns integer begin declare a_count integer; select count (* ) into a_count from depositor where depositor.customer_name = customer_name return a_count; end Find the name and address of each customer that has more than one account. select customer_name, customer_street, customer_city from customer where account_count (customer_name ) > 1

49. 49 Table Functions SQL:2003 added functions that return a relation as a result Example: Return all accounts owned by a given customer create function accounts_of (customer_name char(20) returns table ( account_number char(10), branch_name char(15), balance numeric(12,2)) return table (select account_number, branch_name, balance from account where exists ( select * from depositor where depositor.customer_name = accounts_of.customer_name and depositor.account_number = account.account_number ))

50. 50 Table Functions (cont’d) Usage select * from table (accounts_of (‘Smith’))

51. 51 Procedural Constructs n Compound statement: begin … end, H May contain multiple SQL statements between begin and end. H Local variables can be declared within a compound statements n While and repeat statements: declare n integer default 0; while n < 10 do set n = n + 1 end while repeat set n = n – 1 until n = 0 end repeat

52. 52 Procedural Constructs (Cont.) n For loop H Permits iteration over all results of a query  Example: find total of all balances at the Perryridge branch declare n integer default 0; for r as select balance from account where branch_name = ‘Perryridge’ do set n = n + r.balance end for

53. 53 Procedural Constructs (cont.) Conditional statements (if-then-else) E.g. To find sum of balances for each of three categories of accounts (with balance =1000 and = 5000) if r.balance < 1000 then set l = l + r.balance elseif r.balance < 5000 then set m = m + r.balance else set h = h + r.balance end if SQL:1999 also supports a case statement similar to C case statement Signaling of exception conditions, and declaring handlers for exceptions declare out_of_stock condition declare exit handler for out_of_stock begin ….. signal out-of-stock end  The handler here is exit -- causes enclosing begin..end to be exited  Other actions possible on exception

54. 54 External Language Routines (Cont.) Benefits of external language functions/procedures:  more efficient for many operations, and more expressive power Drawbacks  Code to implement function may need to be loaded into database system and executed in the database system’s address space  risk of accidental corruption of database structures  security risk, allowing users access to unauthorized data  There are alternatives, which give good security at the cost of potentially worse performance  Direct execution in the database system’s space is used when efficiency is more important than security

55. 55 Recursion in SQL SQL:1999 permits recursive view definition Example: find all employee-manager pairs, where the employee reports to the manager directly or indirectly (that is manager’s manager, manager’s manager’s manager, etc.) with recursive empl (employee_name, manager_name ) as ( select employee_name, manager_name from manager union select manager.employee_name, empl.manager_name from manager, empl where manager.manager_name = empl.employe_name) select * from empl This example view, empl, is called the transitive closure of the manager relation

56. 56 The Power of Recursion Recursive views make it possible to write queries, such as transitive closure queries, that cannot be written without recursion or iteration.  Intuition: Without recursion, a non-recursive non-iterative program can perform only a fixed number of joins of manager with itself  This can give only a fixed number of levels of managers  Given a program we can construct a database with a greater number of levels of managers on which the program will not work  The next slide shows a manager relation and each step of the iterative process that constructs empl from its recursive definition. The final result is called the fixed point of the recursive view definition. Recursive views are required to be monotonic. That is, if we add tuples to manger the view contains all of the tuples it contained before, plus possibly more

57. 57 Example of Fixed-Point Computation

58. 58 Advanced SQL Features Create a table with the same schema as an existing table: create table temp_account like account SQL:2003 allows subqueries to occur anywhere a value is required provided the subquery returns only one value. This applies to updates as well SQL:2003 allows subqueries in the from clause to access attributes of other relations in the from clause using the lateral construct: select customer_name, num_accounts from customer, lateral ( select count(*) from account where account.customer_name = customer.customer_name ) as this_customer (num_accounts )

59. 59 Advanced SQL Features (cont’d) Merge construct allows batch processing of updates. Example: relation funds_received (account_number, amount ) has batch of deposits to be added to the proper account in the account relation merge into account as A using (select * from funds_received as F ) on (A.account_number = F.account_number ) when matched then update set balance = balance + F.amount

60. 60 Statistical Databases Problem: how to ensure privacy of individuals while allowing use of data for statistical purposes (e.g., finding median income, average bank balance etc.) Solutions:  System rejects any query that involves fewer than some predetermined number of individuals.  Still possible to use results of multiple overlapping queries to deduce data about an individual  Data pollution -- random falsification of data provided in response to a query.  Random modification of the query itself. There is a tradeoff between accuracy and security.