1. 1 Designing Tables for an Oracle Database System Database Course, Fall 2005

2. 2 From theory to practice The Entity-Relationship model: a convenient way of representing the world. The Relational model: a model of organizing data using tables. Oracle: a database infrastructure which implements the relational model. Converting ER->Relational model is important! SQL(Structured Query Language): A language used to get information from an oracle database.

3. 3 Technicalities Add the following to your.cshrc file: if (-r ~db/oraenv) source ~db/oraenv You will be able to use Oracle after you log out and log in again. You can run Oracle from computers pita, inferno, etc.

4. 4 Sqlplus Oracle is a commercial, hardware-based, heavy(!), program. To connect to it, we use the Sqlplus utility. The Sqlplus program accepts commands in standard SQL and sends them to the Oracle database. The interface creates a “local” database for each user.

5. 5 Connecting to the Oracle Database At the command line prompt, write: Sqlplus (not sqlplus !) This will give you access to the “personal” database of ‘user’ (In other words, to access “your” database, you have to run it from your own CS account). You will be presented with a Sqlplus console, in which you type your commands. To disconnect (and return to your regular shell), type: quit Remember: (almost) Every command must end with a semicolon (;)

6. 6

7. 7 Reminder DISK sailors Reserves Main Memory CPU The database is kept on the disk, so anything you create will be there next time you log on.

8. 8 Running Commands from an.sql File Instead of typing commands into the SQLPLUS terminal, you can load commands from a file (no special format is required). The file name should end with “.sql” Invoke by: 1.Use the command @file from SQLPLUS to load the file file.sql Or: 2. Invoke the SQLPLUS command with the extra parameter @file to load the file at connection: Sqlplus @file

9. 9 Spooling the Output Output can be placed in a file: spool Spooling can be turned off with: spool off

10. 10 Tables The basic element in Oracle is a table. A table has columns (attributes), and rows (tuples). Every column has a Name and Type (of the data it stores), and some columns have constraints. Some tables may have additional constraints.

11. 11 Creating Tables in SQL IdNameDept.Age 0345EyalSales28 0965YairTransport34 7665OriWarehouse31

12. 12 Creating a Table The basic format of the CREATE TABLE command is: CREATE TABLE TableName( Column1 DataType1 ColConstraint, … ColumnN DataTypeN ColConstraint, TableConstraint1, … TableConstraintM );

13. 13Example CREATE TABLE Employee( ID NUMBER NOT NULL, Fname VARCHAR2(20), Lname VARCHAR2(20), Gender CHAR(1), Salary NUMBER(5) NOT NULL, Dept NUMBER );

14. 14 An Example (cont.) Oracle is case insensitive in Column names! If you type describe Employee you get: Name Null? Type ----------- ------------ ------------ ID NOT NULL NUMBER FNAME VARCHAR2(20) LNAME VARCHAR2(20) GENDER CHAR(1) SALARY NOT NULL NUMBER(5) DEPT NUMBER Notice that “describe” describes the structure and not the contents of the table.

15. 15 Examples of Data Types CHAR(n)String of fixed length n (n <= 2000) VARCHAR2(n)Variable length string of size <= n (n <= 4000) CLOBCharacter large object (<= 4GB) BLOBBinary large object (<= 4GB) DATEValid dates (up to seconds) TIMESTAMPValid timestamps (up to milliseconds) NUMBERUp to 40 digits NUMBER(n)Integer of size n NUMBER(n,m) Number of size n with m digits after decimal place OthersXML, Abstract types, etc.

16. 16 What happens if we insert: –'abc' into char(5)? –'abc' into varchar(5)? –'abc' into char(2)? –'abc' into varchar(2)? –105.32 into number(3,2)? –105.32 into number(5,2)? –105.32 into number(4,1)? –105.32 into number(3)? –105.32 into number? –105.1 into number(7,5) ? Why not always use number and not number(n,m)? Why not always use varchar2(4000)? Where is the boolean datatype? “abc“ 105.32 Wrong! 105.32 105.3 105 Wrong!

17. 17 Constraints in Create Table Adding constraints to a table enables the database system to enforce data integrity. However, adding constraints also makes inserting data slower. Different types of constraints: * Not Null* Default Values * Unique * Primary Key * Foreign Key* Check Condition

18. 18 Not Null Constraint CREATE TABLE Employee( SSNNUMBER NOT NULL, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1), SalaryNUMBER(5) NOT NULL, DeptNUMBER );

19. 19 Default Values CREATE TABLE Employee( SSNNUMBER NOT NULL, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNUMBER );

20. 20 Unique Constraint (Syntax 1) CREATE TABLE Employee( SSN NUMBER UNIQUE NOT NULL, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNUMBER );

21. 21 Unique Constraint (Syntax 2) CREATE TABLE Employee( SSNNUMBER NOT NULL, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNUMBER, UNIQUE(SSN) );

22. 22 Unique Constraint (Another Example) CREATE TABLE Employee( SSNNUMBER NOT NULL, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNUMBER, UNIQUE(Fname, Lname) ); Can this be written differently?

23. 23 Primary Key Constraint CREATE TABLE Employee( SSNNUMBER PRIMARY KEY, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNUMBER, UNIQUE(Fname, Lname) ); Primary Key implies: * NOT NULL * UNIQUE. There can only be one primary key.

24. 24 Primary Key Constraint (Syntax 2) CREATE TABLE Employee( SSNNUMBER, Fname VARCHAR2(20), Lname VARCHAR2(20), Gender CHAR(1) DEFAULT(‘F’), Salary NUMBER(5) NOT NULL, DeptNumber NUMBER, UNIQUE(Fname, Lname), PRIMARY KEY(ssn) );

25. 25 Another Table CREATE TABLE Department( DeptNumber NUMBER PRIMARY KEY, Name VARCHAR2(20), ManagerId NUMBER ); Shouldn’t all department numbers in Employee appear in Department ?

26. 26 Foreign Key Constraint CREATE TABLE Employee( IDNUMBER PRIMARY KEY, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNumberNUMBER, UNIQUE(Fname, Lname), FOREIGN KEY (DeptNumber) REFERENCES Department(DeptNumber) ); DeptNumber must be unique (or primary key) in Department

27. 27 Foreign Key Constraint (Syntax 2) CREATE TABLE Employee( IDNUMBER PRIMARY KEY, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’), SalaryNUMBER(5) NOT NULL, DeptNumberNUMBER, UNIQUE(Fname, Lname), FOREIGN KEY (DeptNumber) REFERENCES Department ); NOTE: You can use this syntax only if the name of the fields in both tables are identical

28. 28 Foreign Key IDFNameLNameGenderSallaryDept 02334LarryBirdM23000012 04556MagicJohnsonM27000045 Foreign Key DeptNameManID 12Sales988 45Repair876 Employee Department

29. 29 Understanding Foreign Keys The constraint on the last table should be read as: “The field Dept in Employee is a foreign key that references the field Dept in Department ” Meaning: Every non-null value in the field Dept of Employee must appear in the field Dept of Department. What happens to Employee s in department 312 when Department 312 is removed from the Department table?

30. 30 Deleting a Referenced Value If nothing additional is specified, then Oracle will not allow Department 312 to be deleted if there are Employees working in (referencing to) this department. If the constraint is written as FOREIGN KEY (Dept) REFERENCES Department ON DELETE CASCADE then Employees working in 312 will be deleted automatically from the Employee table, when 312 is deleted from Departments

31. 31 Foreign Keys CREATE TABLE Department( DeptNumber NUMBER PRIMARY KEY, Name VARCHAR2(20), ManagerId NUMBER, FOREIGN KEY (ManagerId) REFERENCES Employee(SSN) ); Do you see a problem in defining these tables and in inserting data now? We should revise the Department table:

32. 32 Foreign Key IDFNameLNameGenderSallaryDeptNum Foreign Key DeptNumNameManID

33. 33 Solution to Cyclic Constraints Add one of the constraints later on (after insertion): CREATE TABLE Department( Dept NUMBER PRIMARY KEY, Name VARCHAR2(20), ManagerId NUMBER); Insert data here… ALTER TABLE Department ADD(FOREIGN KEY (ManagerId) REFERENCES Employee(SSN));

34. 34 Check Conditions A check condition is a Boolean expression: –“And”s and “Or”s of conditions of the type X > 5… On a column: it can refer only to the column On a table: it can refer only to multiple columns in the table

35. 35 Check Constraints CREATE TABLE Employee( SSNNUMBER PRIMARY KEY, Fname VARCHAR2(20), LnameVARCHAR2(20), GenderCHAR(1) DEFAULT(‘F’) CHECK(Gender = ‘F’ or Gender = ‘M’), SalaryNUMBER(5) NOT NULL, CHECK (Gender = ‘M’ or Salary > 10000) );

36. 36 Deleting a Table To delete the table Employee : DROP TABLE Employee; Mind the order of dropping when there are foreign key constraints. Why? Can use: DROP TABLE Employee cascade constraints;

37. 37 Converting ER-Diagrams to Table Definitions

38. 38 General Principals When converting ER diagrams to Relations, we should try to: 1.Reduce duplicate information 2.Constrain as tightly as possible Note: 1.Some scenarios can be represented in different ways. 2.Sometimes we will not be able to fully represent constraints, or will be forced to represent information more than once.

39. 39 Relations vs. Tables We show how to translate ER-Diagrams to table definitions Sometimes, people translate ER-Diagrams to relation definition, which is more abstract than table definitions. –e.g., Employee(SSN, Fname, Lname, Gender, Salary, Dept); –table definitions contain, in addition, constraints and datatypes

40. 40 Simple entity translation General Rule: Create a table with the name of the Entity. There is a column for each attribute The key in the diagram is the primary key of the table Actor id name address birthday

41. 41 Simple entity translation create table Actor(id varchar2(20) primary key, name varchar2(40), birthday date, address varchar2(100)); Actor id name address birthday Relation: Actor (id, name, birthday, address)

42. 42 Translating Entities with Relationships (without constraints) Create tables for the entities as before Create a table with the name of the relationship Relationship table attributes: its own attributes (salary) + all keys of the relating entities (title, id). Q: What is the primary key of the table? A: A composite of both entity keys Q: What foreign keys are needed? A: From the relationship table to the entities Actor id name address birthday Acted In Film title type year salary

43. 43 Translating relationships (without constraints) How would you define the table for ActedIn? Actor id name address birthday Acted In Film title type year salary

44. 44 Translating Recursive Relationships (without constraints) Employee id name address Manages manager worker Relation: Manages (Wid, Mid) What would be the table definition? create table Manages( Eid varchar2(20), Mid varchar2(20), Foreign key Eid references Employee(id), Foreign key Mid references Employee(id), Primary key(Eid, Mid)); If we want to make sure an employee is not his own manager we can express it with Check

45. 45 Translating relationships (key constraints): Option 1 Option 1: Same as without key constraints (3 tables), except that the relationship primary key is…? title. Director id name Directed Film title salary year

46. 46 Translating relationships (key constraints): Option 1 create table Directed( id varchar2(20), title varchar2(40), salary integer, primary key (title), foreign key id references Director, foreign key title references Film); Director id name Directed Film title salary year

47. 47 Translating relationships (key constraints): Option 2 Option 2: Do not create a table for the relationship Add information columns that would have been in the relationship's table to the table of the entity with the key constraint Director id name Directed Film title salary year

48. 48 Translating relationships (key constraints): Option 2 create table Film( title varchar2(40), year integer, primary key (title), id varchar2(20), salary integer, foreign key(id) references Director); Director id name Directed Film title salary year Why couldn’t we do this when there were no constraints?

49. 49 Translating relationships (participation constraints) General Rule: If both participation and key constraint exist, use Option 2 from before (only 2 tables), and: Add the not null constraint on the referncing attribute to ensure that there will always be values for the key of the other entity Director id name Directed Film title salary year

50. 50 Translating relationships (participation constraints) create table Film( title varchar2(40), year integer, id varchar2(20), salary integer, foreign key (id) references Director, primary key (title)); Director id name Directed Film title salary year Where should we add NOT NULL?

51. 51 Translating relationships (participation constraints) How would we translate this? Actor id name Acted In Film title salary year

52. 52 Translating Weak Entity Sets create table award( name varchar2(40), year integer, money number(6,2), o_name varchar2(40), primary key(name, year, o_name), foreign key (o_name) references Organization(name) on delete cascade ) Award Organization Gives year name phone number money

53. 53 Translating ISA: Option 1 create table MoviePerson(... ) create table Actor(id varchar2(20), picture bfile, primary key(id), foreign key (id) references MoviePerson)) create table Director(...) Movie Person ISA id name address picture Director Actor

54. 54 Translating ISA: Option 2 No table for MoviePerson! create table Actor(id varchar2(20), address varchar2(100), name varchar2(20), picture blob, primary key(id)); create table Director(...) Movie Person ISA id name address picture Director Actor

55. 55 Which Option To Choose? What would you choose if: –Actor and Director DO NOT COVER MoviePerson? –Actor OVERLAPS Director?

56. 56 Translating Aggregation Won(title, year, name, Oname, Broadcasted); Director picture Film year type title Acted In salary Award Organization Gives year Oname name phone number Won ID Broad- casted

57. 57 Summary TablesPrimary keyRemarks Simple EntitySingle tableThe entity key a column for each attr. Simple Relationship 3 (2 entities +relationship) For the relation: Both entity keys Foreign keys from rel. Table Key constraint 3 as before or 2 (one for each entity) Key of constrained ent. Foreign keys from rel. Table Foreign key from constr. Entity Key and Participation constr. 2RegularConstrained entity has a non-null f. key

58. 58 TablesPrimary keyRemarks Weak Entity 2: parent and weak entities Weak: its own and parent keys Foreign keys from weak ent. ISA: covers and no overlap 2: only child entities Parent key ISA: otherwise 3: parent and child entities Parent keyForeign keys from child ent. Aggregation3: 2 aggregates and relationship For relationship: keys of both aggregates Foreign keys from relationship table