1. Object-Oriented Database Systems (part 1) CS263 Lecture 17

2. LECTURE PLAN OBJECT DATABASE SYSTEMS PART ONE  Advanced database application areas  Problems associated with RDBMSs  Third Generation DBMSs  What is Object Orientation?  What is an OODBMS?

3. ADVANCED APPLICATION AREAS DATABASES  Computer-Aided Design (CAD).  Computer-Aided Manufacturing (CAM).  Computer-Aided Software Engineering (CASE).  Office Information Systems (OIS).  Multimedia Systems.  Digital Publishing.  Geographic Information Systems (GIS).  Scientific and Medical Systems.

4. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

5. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

6. RELATIONAL DBMSs PROBLEMS - REAL-WORLD OBJECTS CAR C# WHEEL W# SEAT S# TRIM T# C# W# C# Has Part of Has Part of Has ER Diagram - Car

7. RELATIONAL DBMSs PROBLEMS - REAL-WORLD OBJECTS Select * From Car, Wheel, Trim, Seat Where Car.C# = Wheel.C# And Car.C# = Seat.C# And Wheel.W# = Trim.W#; To find out all details about a Car we would have to carry out a large number of (expensive) JOIN operations. Car {C#, Chassis#, NoWheels, NoSeats, etc…} Wheel {W#, C#, Size, Pressure, etc…} Trim {T#, W#, Material, Cost, etc…} Seat {S#, C#, Material, Size, Cost,, etc…} NORMALISATION

8. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

9. RELATIONAL DBMSs PROBLEMS - SEMANTIC OVERLOADING ER Diagram Doctor {D#, Name, Surgery, etc…} Patient {P#, D#, Name, Address, DOB, etc…} DOCTOR D# PATIENT P# D# Oversees Overseen by DOCTOR D# PATIENT P# D# Kills Killed by We do not record the nature of the relationship between doctor and patient!

10. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

11. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

12. RELATIONAL DBMSs PROBLEMS - HOMOGENEOUS DATA STRUCTURE 333.00STRATFORDKHAN456 500.00BARKINGONO400 340.14BARKINGGREEN350 23.17STRATFORDSMITH345 200.00BARKINGGRAY324 1000.00STRATFORDJONES200 BALANCE BRANCHCUSTOMERACCOUNT ACCOUNT TABLE ALL ROWS HAVE THE SAME NUMBER OF ATTRIBUTES ALL VALUES IN A COLUMN ARE OF THE SAME TYPE ALL ATTRIBUTE VALUES ARE ATOMIC

13. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

14. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

15. RELATIONAL DBMSs PROBLEMS - RECURSIVE QUERIES Question - Who does SMITH work for? SMITH Select E2.ENAME From EMP E1, EMP E2 Where E1.MGR = E2.EMPNO And E1.ENAME = “SMITH”; First Level Answer – SMITH works for FORD FORD JONES Select E3.ENAME From EMP E1, EMP E2, EMP E3 Where E1.MGR = E2.EMPNO And E2.MGR = E3.EMPNO And E1.ENAME = “SMITH”; Second Level Answer - SMITH works for JONES KING Select E4.ENAME From EMP E1, EMP E2, EMP E3, EMP E4 Where E1.MGR = E2.EMP And E2.MGR = E3.EMPNO And E3.MGR = E4.EMPNO And E1.ENAME = “SMITH”; Third Level Answer – SMITH works for KING ?

16. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

17. RELATIONAL DBMSs PROBLEMS - IMPEDANCE MISMATCH SQL is a declarative, set-based language that is not computationally complete! This is expensive in terms of application processing time and programming effort, accounting for around 30% of some projects! We therefore have to map sets of data into records using memory structures such as cursors. Database applications require the use of a computationally complete, record-based, procedural language such as C, C++, Java, and PL/SQL.

18. RELATIONAL DBMSs  Poor representation of ‘real world’ entities.  Semantic overloading.  Poor support for integrity and business constraints.  Homogeneous data structure.  Limited operations.  Difficulty handling recursive queries.  Impedance mismatch.  Difficulty with ‘Long Transactions’. PROBLEMS

19. THIRD GENERATION DBMSs

20. Support Complex Active Objects Allow both data and its associated behaviour to be modelled to any level of complexity. Improve Extensibility Allow for the dynamic extension of both allowable data types and the behaviour associated with these types. Reduce the Impedance Mismatch Ensure that there is a seamless integration between the DBMS data model and that of the programming language accessing the data. THIRD GENERATION DBMSs MAIN AIMS

21. OBJECT ORIENTATION

22. Object Model WHAT IS AN ATOMIC (LITERAL) OBJECT? An atomic object is a container for a fixed value and serves the same purpose as a constant in a programming language. An atomic object cannot change its own state. Examples of atomic types and atomic objects Integer - e.g. 1, 2, 3, -5, -45, etc..... Float - e.g. 1.52, -0.3456, 2.000, etc... Boolean - i.e. True or False Char - e.g. a, b, c, @, #, !, etc... String - e.g. “Mark”, “Database Systems”

23. Object Model WHAT IS A (MUTABLE) OBJECT? I am an object! UNIQUE OBJECT IDENTIFIER (OID) NAMEMARK DOB14/02/1964 JOBLECTURER ATTRIBUTES State RELATIONSHIPS CHANGE JOB GET AGE BEHAVIOUR Methods

24. Object Model WHAT IS A CLASS? I am an object! MARK I am also an object! IAN

25. Object Model WHAT IS A CLASS? MARK I am a Person! So am I! IAN PERSON CLASS PERSON NAME DOB JOB CHANGE JOB GET AGE

26. Object Model WHAT IS AN OBJECT IDENTIFIER (OID)? Each object is uniquely identifiable from all other objects. When an object is first created it is assigned a value to identify it. This value is called its Object Identifier.  System generated.  Unique to that object.  Invariant in that it cannot be altered.  Independent of its attribute values.  Invisible to the user.

27. Object Model WHAT IS ENCAPSULATION? GET AGE METHOD CHANGE JOB METHOD NAME:MARK DOB:14/02/64 JOB:LECTURER GET AGE CHANGE JOB OBJECT

28. Object Model WHAT IS A COMPLEX OBJECT? Yes, it’s an object that is made up of other objects! Wheels, Seats, Chassis, Exhaust, Steering Wheel, etc, etc... Is a Car a Complex Object? And… a wheel itself is also a complex object! Tire, Trim, Hub Cap, etc, etc...

29. Object Model WHAT IS A COMPLEX OBJECT? CAR TIRE HUB CAP TRIM TIRE HUB CAP TRIM TIRE HUB CAP TRIM TIRE HUB CAP TRIM CHASSIS WHEEL SEAT REGISTRATION NUMBER

30. Object Model WHAT IS A COMPLEX OBJECT? CAR TIRE HUB CAP TRIM TIRE HUB CAP TRIM TIRE HUB CAP TRIM TIRE HUB CAP TRIM CHASSIS WHEEL REGISTRATION NUMBER SEAT A Wheel IS-PART-OF a Car A Car has a COLLECTION of Wheels

31. Object Model CAR REG-NUMBER:STRING CHASSIS:STRING WHEELS:SET SEATS:SET WHEEL TIRE: STRING HUB CAP: STRING TRIM: STRING WHEEL TIRE: STRING HUB CAP: STRING TRIM: STRING WHEEL TIRE: STRING HUB CAP: STRING TRIM: STRING WHEEL TIRE: STRING HUB CAP: STRING TRIM: STRING SEAT TIRE: STRING HUB CAP: STRING TRIM: STRING SEAT TIRE: STRING HUB CAP: STRING TRIM: STRING SEAT TIRE: STRING HUB CAP: STRING TRIM: STRING SEAT TYPE: STRING COLOUR: STRING POSITION: STRING WHAT IS A COMPLEX OBJECT?

32. Object Model WHAT IS A COLLECTION - SET? SET - An unordered collection of distinct objects of the same type e.g, Customers : SET ; BILL MARK HILDA MARIE CAROLINE An instance of CUSTOMERS

33. Object Model WHAT IS A COLLECTION - BAG? 555-9999 444-3333 555-9999 111-3333 444-3333 An instance of PHONE_CALLS BAG - An unordered collection of objects of the same type e.g, Phone_calls : BAG ;

34. Object Model WHAT IS A COLLECTION - LIST? LIST - An ordered collection of objects of the same type e.g, MachineFaults : LIST ; An instance of MachineFaults Fault at 11:00:01 Fault at 11:00:20 Fault at 11:31:00 Fault at 11:44:33 Fault at 12:00:00

35. Object Model WHAT IS A COLLECTION - ARRAY? ARRAY – Each object is stored at a particular position e.g, StudySchedule : ARRAY ; 0 1 2 3 4 5 6 7 8 9 10 11 12 13 TASK #1 TASK #2 TASK #4 TASK #1 TASK #3 TASK #1 An instance of StudySchedule

36. Object Model WHAT IS A STRUCTURE? A fixed number of named slots, each of which can contain an object of a particular type. e.g, CustomersDetails : STRUCTURE < forenames : List, family_name : String, customer_no : Integer > Marie Rebecca Caroline Campbell 9603456 forenames family_name customer_no An instance of CustomerDetails

37. Object Model WHAT IS INHERITANCE? Person name address telephone_no change_name (...) change_address (...) Employee employee_no promote(...) pay_employee (...) Customer customer_no place_order(...) make_payment(...) TradeCustomer trade_discount% place_order(...) make_payment(...) IS-A

38. Object Model WHAT IS MULTIPLE INHERITANCE? Person name address telephone_no change_name (...) change_address (...) Employee employee_no promote(...) pay_employee (...) Customer customer_no place_order(...) make_payment(...) Employee_Customer staff_discount_card place_order(...) make_payment(...) TradeCustomer trade_discount% place_order(...) make_payment(...) IS-A

39. Object Model WHAT ARE OBJECT RELATIONSHIPS? Child.... Mother.... * child_of 1 mother_of one-to-many Husband.... Wife.... 1 husband_of 1 wife_of one-to-one Child.... Parent.... * child_of * parent_of many-to-many

40. Object Model WHAT ARE METHODS AND MESSAGES? GET AGE METHOD BODY CHANGE JOB METHOD BODY NAME:MARK DOB:14/02/64 JOB:LECTURER GET AGE MESSAGE CHANGE JOB MESSAGE USER PROGRAM OBJECT DISK

41. Object Model WHAT IS POLYMORPHISM? CLOCK... SetTime () SetAlarm () ShowTime () ANALOGUE CLOCK... SetTime () SetAlarm () ShowTime () DIGITAL CLOCK... SetTime () SetAlarm () ShowTime () 11:00 PM DIFFERENT TYPES OF OBJECT RESPOND DIFFERENTLY TO THE SAME MESSAGE

42. Object Model WHAT IS OVERIDING? When a sub-class’s method body is used rather than the body of the super-class’s method it is known as overriding. CUSTOMER Customer No. PlaceOrder() MakePayment() TRADE CUSTOMER TradeDiscount% PlaceOrder() METHOD BODY 1. Create order details 2. Calculate total cost METHOD BODY 1. Create order details 2. Calculate total cost 3. Apply Trade Discount SUPER-CLASS SUB-CLASS IS-A

43. Object Model WHAT IS LATE BINDING? Late or dynamic binding is the ability of the runtime system to determine which method body to execute depending on the type of an object. CUSTOMER TIRE: STRING HUB CAP: STRING TRIM: STRING Trade Customer TIRE: STRING HUB CAP: STRING TRIM: STRING CUSTOMER TIRE: HUB CAP: TRIM: STRIN Trade Customer CUSTOMER NO PLACE_ORDER MAKE_PAYMENT Customers := SET FOR x IN Customers DO x.PLACE_ORDER END Where x := an individual Customer Object! It doesn’t matter if a customer is a trade customer, late binding ensures the appropriate PLACE_ORDER method body is called!

44. OODBMS

45. WHAT IS AN OODBMS? Object Oriented Database Management Systems (OODBMSs) are an attempt at marrying the power of Object Oriented Programming Languages with the persistence and associated technologies of a DBMS. OOPLsDBMSs Complex ObjectsPersistence Object IdentityDisc Management Methods & MessagesData Sharing InheritanceReliability PolymorphismSecurity ExtensibilityAd Hoc Querying Computational Completeness OBJECT ORIENTED DATABASE MANAGEMENT SYSTEM

46. OODBMS WHAT AN OODBMS SHOULD SUPPORT?  Atomic and complex objects  Methods and messages  Object Identity  Single inheritance  Polymorphism - overloading and late-binding  Persistence  Shared Objects In addition an OODBMS can optionally support  Multiple inheritance  Exception messages  Distribution  Long Transactions  Versions