1. 1 © Prentice Hall, 2002 Chapter 7: SQL Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden

2. Chapter 7 2 © Prentice Hall, 2002 SQL Is: Structured Query Language The standard for relational database management systems (RDBMS) SQL-92 Standard -- Purpose: – Specify syntax/semantics for data definition and manipulation – Define data structures – Enable portability – Specify minimal (level 1) and complete (level 2) standards – Allow for later growth/enhancement to standard

3. Chapter 7 3 © Prentice Hall, 2002 Benefits of a Standardized Relational Language Reduced training costs Productivity Application portability Application longevity Reduced dependence on a single vendor Cross-system communication

4. Chapter 7 4 © Prentice Hall, 2002 SQL Environment Catalog – a set of schemas that constitute the description of a database Schema – The structure that contains descriptions of objects created by a user (base tables, views, constraints) Data Definition Language (DDL): – Commands that define a database, including creating, altering, and dropping tables and establishing constraints Data Manipulation Language (DML) – Commands that maintain and query a database Data Control Language (DCL) – Commands that control a database, including administering privileges and committing data

5. Chapter 7 5 © Prentice Hall, 2002 Figure 7-1: A simplified schematic of a typical SQL environment, as described by the SQL-92 standard

6. Chapter 7 6 © Prentice Hall, 2002 SQL Data types (from Oracle8) String types – CHAR(n) – fixed-length character data, n characters long Maximum length = 2000 bytes – VARCHAR2(n) – variable length character data, maximum 4000 bytes – LONG – variable-length character data, up to 4GB. Maximum 1 per table Numeric types – NUMBER(p,q) – general purpose numeric data type – INTEGER(p) – signed integer, p digits wide – FLOAT(p) – floating point in scientific notation with p binary digits precision Date/time type – DATE – fixed-length date/time in dd-mm-yy form

7. Chapter 7 7 © Prentice Hall, 2002 Figure 7-4: DDL, DML, DCL, and the database development process

8. Chapter 7 8 © Prentice Hall, 2002 SQL Database Definition Data Definition Language (DDL) Major CREATE statements: – CREATE SCHEMA – defines a portion of the database owned by a particular user – CREATE TABLE – defines a table and its columns – CREATE VIEW – defines a logical table from one or more views Other CREATE statements: CHARACTER SET, COLLATION, TRANSLATION, ASSERTION, DOMAIN

9. Chapter 7 9 © Prentice Hall, 2002 Table Creation Figure 7-5: General syntax for CREATE TABLE Steps in table creation: 1.Identify data types for attributes 2.Identify columns that can and cannot be null 3.Identify columns that must be unique (candidate keys) 4.Identify primary key- foreign key mates 5.Determine default values 6.Identify constraints on columns (domain specifications) 7.Create the table and associated indexes

10. Chapter 7 10 © Prentice Hall, 2002 Figure 7-3: Sample Pine Valley Furniture data customers orders order lines products

11. Chapter 7 11 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture

12. Chapter 7 12 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Defining attributes and their data types

13. Chapter 7 13 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Non-nullable specifications Note: primary keys should not be null

14. Chapter 7 14 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Identifying primary keys This is a composite primary key

15. Chapter 7 15 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Identifying foreign keys and establishing relationships

16. Chapter 7 16 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Default values and domain constraints

17. Chapter 7 17 © Prentice Hall, 2002 Figure 7-6: SQL database definition commands for Pine Valley Furniture Overall table definitions

18. Chapter 7 18 © Prentice Hall, 2002 Unique Parameters for MySQL

19. Chapter 7 19 © Prentice Hall, 2002 For example…

20. Chapter 7 20 © Prentice Hall, 2002 Numeric Data Types BOOLEAN – These are synonyms for TINYINT(1). A value of zero is considered false. Non-zero values are considered true. SMALLINT[(M)] [UNSIGNED] [ZEROFILL] – A small integer. The signed range is -32768 to 32767. The unsigned range is 0 to 65535. MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL] – A medium-size integer. The signed range is -8388608 to 8388607. The unsigned range is 0 to 16777215.

21. Chapter 7 21 © Prentice Hall, 2002 Numeric Data Types INT[(M)] [UNSIGNED] [ZEROFILL] – A normal-size integer. The signed range is - 2147483648 to 2147483647. The unsigned range is 0 to 4294967295. INTEGER[(M)] [UNSIGNED] [ZEROFILL] – This is a synonym for INT. FLOAT(p) [UNSIGNED] [ZEROFILL] – A floating-point number. p represents the precision. It can be from 0 to 24 for a single-precision floating-point number and from 25 to 53 for a double-precision floating-point number.

22. Chapter 7 22 © Prentice Hall, 2002 Numeric Data Types DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL] – An unpacked fixed-point number. Behaves like a CHAR column; ``unpacked'' means the number is stored as a string, using one character for each digit of the value. M is the total number of digits and D is the number of decimals. The decimal point and (for negative numbers) the `-' sign are not counted in M, although space for them is reserved. If D is 0, values have no decimal point or fractional part. DEC[(M[,D])] [UNSIGNED] [ZEROFILL] NUMERIC[(M[,D])] [UNSIGNED] [ZEROFILL] FIXED[(M[,D])] [UNSIGNED] [ZEROFILL] – These are synonyms for DECIMAL. The FIXED synonym was added in MySQL 4.1.0 for compatibility with other servers.

23. Chapter 7 23 © Prentice Hall, 2002 Using and Defining Views Views provide users controlled access to tables Advantages of views: – Simplify query commands – Provide data security – Enhance programming productivity CREATE VIEW command

24. Chapter 7 24 © Prentice Hall, 2002 View Terminology Base Table – A table containing the raw data Dynamic View – A “virtual table” created dynamically upon request by a user. – No data actually stored; instead data from base table made available to user – Based on SQL SELECT statement on base tables or other views Materialized View – Copy or replication of data – Data actually stored – Must be refreshed periodically to match the corresponding base tables

25. Chapter 7 25 © Prentice Hall, 2002 String Types CHAR(M) [BINARY | ASCII | UNICODE] – A fixed-length string that is always right-padded with spaces to the specified length when stored. M represents the column length. The range of M is 0 to 255 characters VARCHAR(M) [BINARY] – A variable-length string. M represents the maximum column length. The range of M is 0 to 255 characters BLOB and TEXT – A column with a maximum length of 65,535 (2^16 -1) characters. Used for storing text that is longer than that in CHAR and VARCHAR.

26. Chapter 7 26 © Prentice Hall, 2002 Date and Time Types DATE – A date. The supported range is '1000-01-01' to '9999-12-31'. MySQL displays DATE values in 'YYYY-MM-DD' format, but allows you to assign values to DATE columns using either strings or numbers. DATETIME – A date and time combination. The supported range is '1000-01-01 00:00:00' to '9999-12-31 23:59:59'. MySQL displays DATETIME values in 'YYYY- MM-DD HH:MM:SS' format, but allows you to assign values to DATETIME columns using either strings or numbers.

27. Chapter 7 27 © Prentice Hall, 2002 Date and Time Types TIME – A time. The range is '-838:59:59' to '838:59:59'. MySQL displays TIME values in 'HH:MM:SS' format, but allows you to assign values to TIME columns using either strings or numbers. YEAR[(2|4)] – A year in two-digit or four-digit format. The default is four-digit format. In four-digit format, the allowable values are 1901 to 2155, and 0000. TIMESTAMP[(M)] – A timestamp. The range is '1970-01-01 00:00:00' to partway through the year 2037. A TIMESTAMP column is useful for recording the date and time of an INSERT or UPDATE operation. The first TIMESTAMP column in a table is automatically set to the date and time of the most recent operation if you don't assign it a value yourself. You can also set any TIMESTAMP column to the current date and time by assigning it a NULL value.

28. Chapter 7 28 © Prentice Hall, 2002 Changing and Removing Tables ALTER TABLE statement allows you to change column specifications: – ALTER TABLE CUSTOMER_T ADD (TYPE VARCHAR(2)) DROP TABLE statement allows you to remove tables from your schema: – DROP TABLE CUSTOMER_T

29. Chapter 7 29 © Prentice Hall, 2002 Alter Table Command

30. Chapter 7 30 © Prentice Hall, 2002 Alter Table Command ALTER TABLE client DROP primary key

31. Chapter 7 31 © Prentice Hall, 2002 Dropping Tables DROP [TEMPORARY] TABLE [IF EXISTS] tbl_name [, tbl_name, …]

32. Chapter 7 32 © Prentice Hall, 2002 Delete Statement Removes rows from a table Delete certain rows – DELETE FROM CUSTOMER_T WHERE STATE = ‘HI’; Delete all rows – DELETE FROM CUSTOMER_T;

33. Chapter 7 33 © Prentice Hall, 2002 Sample CREATE VIEW CREATE VIEW EXPENSIVE_STUFF_V AS SELECT PRODUCT_ID, PRODUCT_NAME, UNIT_PRICE FROM PRODUCT_T WHERE UNIT_PRICE >300 WITH CHECK_OPTION; View has a name View is based on a SELECT statement CHECK_OPTION works only for updateable views and prevents updates that would create rows not included in the view MySQL does not support Views in v. 4.1, but will in 5.0

34. Chapter 7 34 © Prentice Hall, 2002 Table 7-2: Pros and Cons of Using Dynamic Views

35. Chapter 7 35 © Prentice Hall, 2002 Data Integrity Controls Referential integrity – constraint that ensures that foreign key values of a table must match primary key values of a related table in 1:M relationships Restricting: – Deletes of primary records – Updates of primary records – Inserts of dependent records

36. Chapter 7 36 © Prentice Hall, 2002 Figure 7-7: Ensuring data integrity through updates

37. Chapter 7 37 © Prentice Hall, 2002 Schema Definition Control processing/storage efficiency: – Choice of indexes – File organizations for base tables – File organizations for indexes – Data clustering – Statistics maintenance Creating indexes – Speed up random/sequential access to base table data – Example CREATE INDEX NAME_IDX ON CUSTOMER_T(CUSTOMER_NAME) This makes an index for the CUSTOMER_NAME field of the CUSTOMER_T table

38. Chapter 7 38 © Prentice Hall, 2002 Insert Statement Adds data to a table INSERT Syntax INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO] tbl_name [(col_name,...)] VALUES ({expr | DEFAULT},...),(...),... [ ON DUPLICATE KEY UPDATE col_name=expr,... ] Or: INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO] tbl_name SET col_name={expr | DEFAULT},... [ ON DUPLICATE KEY UPDATE col_name=expr,... ] Or: INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO

39. Chapter 7 39 © Prentice Hall, 2002 Insert Statement Inserting into a table – INSERT INTO CUSTOMER_T VALUES (001, ‘CONTEMPORARY Casuals’, 1355 S. Himes Blvd.’, ‘Gainesville’, ‘FL’, 32601); Inserting a record that has some null attributes requires identifying the fields that actually get data – INSERT INTO PRODUCT_T (PRODUCT_ID, PRODUCT_DESCRIPTION,PRODUCT_FINISH, STANDARD_PRICE, PRODUCT_ON_HAND) VALUES (1, ‘End Table’, ‘Cherry’, 175, 8); Inserting from another table – INSERT INTO CA_CUSTOMER_T SELECT * FROM CUSTOMER_T WHERE STATE = ‘CA’;

40. Chapter 7 40 © Prentice Hall, 2002 Update Statement Modifies data in existing rows UPDATE PRODUCT_T SET UNIT_PRICE = 775 WHERE PRODUCT_ID = 7;

41. Chapter 7 41 © Prentice Hall, 2002 String Functions Visit http://dev.mysql.com/doc/mysql/en/String_f unctions.html#IDX1257 for a complete list http://dev.mysql.com/doc/mysql/en/String_f unctions.html#IDX1257

42. Chapter 7 42 © Prentice Hall, 2002 The SELECT Statement Used for queries on single or multiple tables Clauses of the SELECT statement: – SELECT List the columns (and expressions) that should be returned from the query – FROM Indicate the table(s) or view(s) from which data will be obtained – WHERE Indicate the conditions under which a row will be included in the result – GROUP BY Indicate categorization of results – HAVING Indicate the conditions under which a category (group) will be included – ORDER BY Sorts the result according to specified criteria

43. Chapter 7 43 © Prentice Hall, 2002 Figure 7-8: SQL statement processing order (adapted from van der Lans, p.100)

44. Chapter 7 44 © Prentice Hall, 2002 SELECT Example Find products with standard price less than $275 SELECT PRODUCT_NAME, STANDARD_PRICE FROM PRODUCT_V WHERE STANDARD_PRICE < 275 Table 7-3: Comparison Operators in SQL

45. Chapter 7 45 © Prentice Hall, 2002 SELECT Example with ALIAS Alias is an alternative column or table name SELECT CUST.CUSTOMER AS NAME, CUST.CUSTOMER_ADDRESS FROM CUSTOMER_V CUST WHERE NAME = ‘Home Furnishings’;

46. Chapter 7 46 © Prentice Hall, 2002 SELECT Example Using a Function Using the COUNT aggregate function to find totals SELECT COUNT(*) FROM ORDER_LINE_V WHERE ORDER_ID = 1004; Note: with aggregate functions you can’t have single- valued columns included in the SELECT clause

47. Chapter 7 47 © Prentice Hall, 2002 SELECT Example – Boolean Operators AND, OR, and NOT Operators for customizing conditions in WHERE clause SELECT PRODUCT_DESCRIPTION, PRODUCT_FINISH, STANDARD_PRICE FROM PRODUCT_V WHERE (PRODUCT_DESCRIPTION LIKE ‘%Desk’ OR PRODUCT_DESCRIPTION LIKE ‘%Table’) AND UNIT_PRICE > 300; Note: the LIKE operator allows you to compare strings using wildcards. For example, the % wildcard in ‘%Desk’ indicates that all strings that have any number of characters preceding the word “Desk” will be allowed

48. Chapter 7 48 © Prentice Hall, 2002 SELECT Example – Sorting Results with the ORDER BY Clause Sort the results first by STATE, and within a state by CUSTOMER_NAME SELECT CUSTOMER_NAME, CITY, STATE FROM CUSTOMER_V WHERE STATE IN (‘FL’, ‘TX’, ‘CA’, ‘HI’) ORDER BY STATE, CUSTOMER_NAME; Note: the IN operator in this example allows you to include rows whose STATE value is either FL, TX, CA, or HI. It is more efficient than separate OR conditions

49. Chapter 7 49 © Prentice Hall, 2002 SELECT Example – Categorizing Results Using the GROUP BY Clause For use with aggregate functions – Scalar aggregate: single value returned from SQL query with aggregate function – Vector aggregate: multiple values returned from SQL query with aggregate function (via GROUP BY) SELECT STATE, COUNT(STATE) FROM CUSTOMER_V GROUP BY STATE; Note: you can use single-value fields with aggregate functions if they are included in the GROUP BY clause

50. Chapter 7 50 © Prentice Hall, 2002 SELECT Example – Qualifying Results by Categories Using the HAVING Clause For use with GROUP BY SELECT STATE, COUNT(STATE) FROM CUSTOMER_V GROUP BY STATE HAVING COUNT(STATE) > 1; Like a WHERE clause, but it operates on groups (categories), not on individual rows. Here, only those groups with total numbers greater than 1 will be included in final result