Chapter 8: Object-Oriented Databases
Chapter 8: Object-Oriented Databases! Need for Complex Data Types! The Object-Oriented Data Model! Object-Oriented Languages! Persistent Programming Languages! Persistent C SystemsDatabase System Concepts8.1 Silberschatz, Korth and SudarshanNeed for Complex Data Types! Traditional database applications in data processing hadconceptually simple data types! Relatively few data types, first normal form holds! Complex data types have grown more important in recent years! E.g. Addresses can be viewed as a" Single string, or" Separate attributes for each part, or" Composite attributes (which are not in first normal form)! E.g. it is often convenient to store multivalued attributes as-is,without creating a separate relation to store the values in firstnormal form! Applications! computer-aided design, computer-aided software engineering! multimedia and image databases, and document/hypertextdatabases.Database System Concepts8.2 Silberschatz, Korth and Sudarshan1
Object-Oriented Data Model! Loosely speaking, an object corresponds to an entity in the E-R model.! The object-oriented paradigm is based on encapsulating codeand data related to an object into single unit.! The object-oriented data model is a logical data model (likethe E-R model).! Adaptation of the object-oriented programming paradigm (e.g.,Smalltalk, C ) to database systems.Database System Concepts8.3 Silberschatz, Korth and SudarshanObject Structure! An object has associated with it:! A set of variables that contain the data for the object. The value ofeach variable is itself an object.! A set of messages to which the object responds; each message mayhave zero, one, or more parameters.! A set of methods, each of which is a body of code to implement amessage; a method returns a value as the response to the message! The physical representation of data is visible only to theimplementor of the object! Messages and responses provide the only external interface to anobject.! The term message does not necessarily imply physical messagepassing. Messages can be implemented as procedureinvocations.Database System Concepts8.4 Silberschatz, Korth and Sudarshan2
Messages and Methods! Methods are programs written in general-purpose languagewith the following features! only variables in the object itself may be referenced directly! data in other objects are referenced only by sending messages.! Methods can be read-only or update methods! Read-only methods do not change the value of the object! Strictly speaking, every attribute of an entity must berepresented by a variable and two methods, one to read andthe other to update the attribute! e.g., the attribute address is represented by a variable addressand two messages get-address and set-address.! For convenience, many object-oriented data models permit directaccess to variables of other objects.Database System Concepts8.5 Silberschatz, Korth and SudarshanObject Classes! Similar objects are grouped into a class; each such object iscalled an instance of its class! All objects in a class have the same! Variables, with the same types! message interface! methodsThe may differ in the values assigned to variables! Example: Group objects for people into a person class! Classes are analogous to entity sets in the E-R modelDatabase System Concepts8.6 Silberschatz, Korth and Sudarshan3
Class Definition Exampleclass employee {/*Variables */string name;string address;datestart-date;intsalary;/* Messages */intannual-salary();string get-name();string get-address();intset-address(string new-address);intemployment-length();};! Methods to read and set the other variables are also needed withstrict encapsulation! Methods are defined separately! E.g. int employment-length() { return today() – start-date;}int set-address(string new-address) { address new-address;}Database System Concepts8.7 Silberschatz, Korth and SudarshanInheritance! E.g., class of bank customers is similar to class of bankemployees, although there are differences! both share some variables and messages, e.g., name and address.! But there are variables and messages specific to each class e.g.,salary for employees and credit-rating for customers.! Every employee is a person; thus employee is a specialization ofperson! Similarly, customer is a specialization of person.! Create classes person, employee and customer! variables/messages applicable to all persons associated with classperson.! variables/messages specific to employees associated with classemployee; similarly for customerDatabase System Concepts8.8 Silberschatz, Korth and Sudarshan4
Inheritance (Cont.)! Place classes into a specialization/IS-A hierarchy! variables/messages belonging to class person areinherited by class employee as well as customer! Result is a class hierarchyNote analogy with ISA Hierarchy in the E-R modelDatabase System Concepts8.9 Silberschatz, Korth and SudarshanClass Hierarchy Definitionclass person{string name;string address:};class customer isa person {int credit-rating;};class employee isa person {date start-date;int salary;};class officer isa employee {int office-number,int expense-account-number,};.Database System Concepts8.10 Silberschatz, Korth and Sudarshan5
Class Hierarchy Example (Cont.)!Full variable list for objects in the class officer:! office-number, expense-account-number: defined locally! start-date, salary: inherited from employee! name, address: inherited from person!Methods inherited similar to variables.!Substitutability — any method of a class, say person, can be invokedequally well with any object belonging to any subclass, such assubclass officer of person.!Class extent: set of all objects in the class. Two options:1. Class extent of employee includes all officer, teller and secretary objects.2. Class extent of employee includes only employee objects that are not in asubclass such as officer, teller, or secretary#This is the usual choice in OO systems#Can access extents of subclasses to find all objects ofsubtypes of employeeDatabase System Concepts8.11 Silberschatz, Korth and SudarshanExample of Multiple InheritanceClass DAG for banking example.Database System Concepts8.12 Silberschatz, Korth and Sudarshan6
Multiple Inheritance! With multiple inheritance a class may have more than one superclass.! The class/subclass relationship is represented by a directed acyclic graph(DAG)! Particularly useful when objects can be classified in more than one way,which are independent of each other" E.g. temporary/permanent is independent of Officer/secretary/teller" Create a subclass for each combination of subclasses– Need not create subclasses for combinations that are not possible inthe database being modeled! A class inherits variables and methods from all its superclasses! There is potential for ambiguity when a variable/message N with thesame name is inherited from two superclasses A and B! No problem if the variable/message is defined in a shared superclass! Otherwise, do one of the following" flag as an error," rename variables (A.N and B.N)" choose one.Database System Concepts8.13 Silberschatz, Korth and SudarshanMore Examples of Multiple Inheritance! Conceptually, an object can belong to each of severalsubclasses! A person can play the roles of student, a teacher or footballPlayer,or any combination of the three" E.g., student teaching assistant who also play football! Can use multiple inheritance to model “roles” of an object! That is, allow an object to take on any one or more of a set of types! But many systems insist an object should have a most-specificclass! That is, there must be one class that an object belongs to which isa subclass of all other classes that the object belongs to! Create subclasses such as student-teacher andstudent-teacher-footballPlayer for each combination! When many combinations are possible, creatingsubclasses for each combination can become cumbersomeDatabase System Concepts8.14 Silberschatz, Korth and Sudarshan7
Object Identity! An object retains its identity even if some or all of the valuesof variables or definitions of methods change over time.! Object identity is a stronger notion of identity than inprogramming languages or data models not based on objectorientation.! Value – data value; e.g. primary key value used in relationalsystems.! Name – supplied by user; used for variables in procedures.! Built-in – identity built into data model or programminglanguage." no user-supplied identifier is required." Is the form of identity used in object-oriented systems.Database System Concepts8.15 Silberschatz, Korth and SudarshanObject Identifiers! Object identifiers used to uniquely identify objects! Object identifiers are unique:" no two objects have the same identifier" each object has only one object identifier! E.g., the spouse field of a person object may be an identifier ofanother person object.! can be stored as a field of an object, to refer to another object.! Can be" system generated (created by database) or" external (such as social-security number)! System generated identifiers:" Are easier to use, but cannot be used across database systems" May be redundant if unique identifier already existsDatabase System Concepts8.16 Silberschatz, Korth and Sudarshan8
Object Containment! Each component in a design may contain other components! Can be modeled as containment of objects. Objects containing;other objects are called composite objects.! Multiple levels of containment create a containment hierarchy! links interpreted as is-part-of, not is-a.! Allows data to be viewed at different granularities by differentusers.Database System Concepts8.17 Silberschatz, Korth and SudarshanObject-Oriented Languages! Object-oriented concepts can be used in different ways! Object-orientation can be used as a design tool, and beencoded into, for example, a relational database#analogous to modeling data with E-R diagram and thenconverting to a set of relations)! The concepts of object orientation can be incorporated into aprogramming language that is used to manipulate thedatabase." Object-relational systems – add complex types andobject-orientation to relational language." Persistent programming languages – extend object-oriented programming language to deal with databasesby adding concepts such as persistence and collections.Database System Concepts8.18 Silberschatz, Korth and Sudarshan9
Persistent Programming Languages! Persistent Programming languages allow objects to be createdand stored in a database, and used directly from a programminglanguage! allow data to be manipulated directly from the programming language" No need to go through SQL.! No need for explicit format (type) changes" format changes are carried out transparently by system" Without a persistent programming language, format changesbecomes a burden on the programmer– More code to be written– More chance of bugs! allow objects to be manipulated in-memory" no need to explicitly load from or store to the database– Saved code, and saved overhead of loading/storing largeamounts of dataDatabase System Concepts8.19 Silberschatz, Korth and SudarshanPersistent Prog. Languages (Cont.)! Drawbacks of persistent programming languages! Due to power of most programming languages, it is easy to makeprogramming errors that damage the database.! Complexity of languages makes automatic high-level optimizationmore difficult.! Do not support declarative querying as well as relational databasesDatabase System Concepts8.20 Silberschatz, Korth and Sudarshan10
Persistence of Objects! Approaches to make transient objects persistent includeestablishing! Persistence by Class – declare all objects of a class to bepersistent; simple but inflexible.! Persistence by Creation – extend the syntax for creating objects tospecify that that an object is persistent.! Persistence by Marking – an object that is to persist beyondprogram execution is marked as persistent before programtermination.! Persistence by Reachability - declare (root) persistent objects;objects are persistent if they are referred to (directly or indirectly)from a root object." Easier for programmer, but more overhead for database system" Similar to garbage collection used e.g. in Java, whichalso performs reachability testsDatabase System Concepts8.21 Silberschatz, Korth and SudarshanObject Identity and Pointers! A persistent object is assigned a persistent object identifier.! Degrees of permanence of identity:! Intraprocedure – identity persists only during the executions of asingle procedure! Intraprogram – identity persists only during execution of a singleprogram or query.! Interprogram – identity persists from one program execution toanother, but may change if the storage organization is changed! Persistent – identity persists throughout program executions andstructural reorganizations of data; required for object-orientedsystems.Database System Concepts8.22 Silberschatz, Korth and Sudarshan11
Object Identity and Pointers (Cont.)! In O-O languages such as C , an object identifier isactually an in-memory pointer.! Persistent pointer – persists beyond program execution! can be thought of as a pointer into the database" E.g. specify file identifier and offset into the file! Problems due to database reorganization have to be dealtwith by keeping forwarding pointersDatabase System Concepts8.23 Silberschatz, Korth and SudarshanStorage and Access of Persistent ObjectsHow to find objects in the database:! Name objects (as you would name files)! Cannot scale to large number of objects.! Typically given only to class extents and other collections ofobjects, but not objects.! Expose object identifiers or persistent pointers to the objects! Can be stored externally.! All objects have object identifiers.! Store collections of objects, and allow programs to iterateover the collections to find required objects! Model collections of objects as collection types! Class extent - the collection of all objects belonging to theclass; usually maintained for all classes that can have persistentobjects.Database System Concepts8.24 Silberschatz, Korth and Sudarshan12
Persistent C Systems! C language allows support for persistence to be added withoutchanging the language! Declare a class called Persistent Object with attributes and methodsto support persistence! Overloading – ability to redefine standard function names andoperators (i.e., , –, the pointer deference operator – ) when appliedto new types! Template classes help to build a type-safe type system supportingcollections and persistent types.! Providing persistence without extending the C language is! relatively easy to implement! but more difficult to use! Persistent C systems that add features to the C languagehave been built, as also systems that avoid changing thelanguageDatabase System Concepts8.25 Silberschatz, Korth and SudarshanODMG C Object Definition Language! The Object Database Management Group is an industryconsortium aimed at standardizing object-oriented databases! in particular persistent programming languages! Includes standards for C , Smalltalk and Java! ODMG-93! ODMG-2.0 and 3.0 (which is 2.0 plus extensions to Java)" Our description based on ODMG-2.0! ODMG C standard avoids changes to the C language! provides functionality via template classes and class librariesDatabase System Concepts8.26 Silberschatz, Korth and Sudarshan13
ODMG Types! Template class d Ref class used to specify references(persistent pointers)! Template class d Set class used to define sets of objects.! Methods include insert element(e) and delete element(e)! Other collection classes such as d Bag (set with duplicatesallowed), d List and d Varray (variable length array) alsoprovided.! d version of many standard types provided, e.g. d Long andd string! Interpretation of these types is platform independent! Dynamically allocated data (e.g. for d string) allocated in thedatabase, not in main memoryDatabase System Concepts8.27 Silberschatz, Korth and SudarshanODMG C ODL: Exampleclass Branch : public d Object { .}class Person : public d Object {public:d String name;// should not use String!d String address;};class Account : public d Object {private:d Longbalance;public:d Longnumber;d Set d Ref Customer owners;};intintDatabase System Conceptsfind balance();update balance(int delta);8.28 Silberschatz, Korth and Sudarshan14
ODMG C ODL: Example (Cont.)class Customer : public Person {public:d Datemember from;d Longcustomer id;d Ref Branch home branch;d Set d Ref Account accounts; };Database System Concepts8.29 Silberschatz, Korth and SudarshanImplementing Relationships! Relationships between classes implemented by references! Special reference types enforces integrity by adding/removinginverse links.! Type d Rel Ref Class, InvRef is a reference to Class, whereattribute InvRef of Class is the inverse reference.! Similarly, d Rel Set Class, InvRef is used for a set of references! Assignment method ( ) of class d Rel Ref is overloaded! Uses type definition to automatically find and update the inverselink! Frees programmer from task of updating inverse links! Eliminates possibility of inconsistent links! Similarly, insert element() and delete element() methods ofd Rel Set use type definition to find and update the inverse linkautomaticallyDatabase System Concepts8.30 Silberschatz, Korth and Sudarshan15
Implementing Relationships! E.g.extern const char owners[ ], accounts[ ];class Account : public d.Object { .d Rel Set Customer, accounts owners;}// . Since strings can’t be used in templates const char owners “owners”;const char accounts “accounts”;Database System Concepts8.31 Silberschatz, Korth and SudarshanODMG C Object Manipulation Language! Uses persistent versions of C operators such as new(db)d Ref Account account new(bank db, “Account”) Account;! new allocates the object in the specified database, rather than inmemory.! The second argument (“Account”) gives typename used in thedatabase.! Dereference operator - when applied on a d Ref Account reference loads the referenced object in memory (if not alreadypresent) before continuing with usual C dereference.! Constructor for a class – a special method to initialize objectswhen they are created; called automatically on new call.! Class extents maintained automatically on object creation anddeletion! Only for classes for which this feature has been specified" Specification via user interface, not C ! Automatic maintenance of class extents not supported inearlier versions of ODMGDatabase System Concepts8.32 Silberschatz, Korth and Sudarshan16
ODMG C OML: Database and ObjectFunctions! Class d Database provides methods to! open a database:open(databasename)! give names to objects:set object name(object, name)! look up objects by name: lookup object(name)! rename objects:rename object(oldname, newname)! close a database (close());! Class d Object is inherited by all persistent classes.! provides methods to allocate and delete objects! method mark modified() must be called before an object isupdated." Is automatically called when object is createdDatabase System Concepts8.33 Silberschatz, Korth and SudarshanODMG C OML: Exampleint create account owner(String name, String Address){Database bank db.obj;Database * bank db & bank db.obj;bank db open(“Bank-DB”);d.Transaction Trans;Trans.begin();d Ref Account account new(bank db) Account;d Ref Customer cust new(bank db) Customer;cust- name - name;cust- address address;cust- accounts.insert element(account);. Code to initialize other fieldsTrans.commit();}Database System Concepts8.34 Silberschatz, Korth and Sudarshan17
ODMG C OML: Example (Cont.)! Class extents maintained automatically in the database.! To access a class extent:d Extent Customer customerExtent(bank db);! Class d Extent provides methodd Iterator T create iterator()to create an iterator on the class extent! Also provides select(pr
2 Database System Concepts 8.3 Silberschatz, Korth and Sudarshan Object-Oriented Data Model! Loosely speaking, an object corresponds to an entity in the E- R model.! The object-oriented paradigm is based on encapsulating code and data related to an object into single unit.! The object-oriented data model is a logical data model (like
Part One: Heir of Ash Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 Chapter 21 Chapter 22 Chapter 23 Chapter 24 Chapter 25 Chapter 26 Chapter 27 Chapter 28 Chapter 29 Chapter 30 .
Object Class: Independent Protection Layer Object: Safety Instrumented Function SIF-101 Compressor S/D Object: SIF-129 Tower feed S/D Event Data Diagnostics Bypasses Failures Incidences Activations Object Oriented - Functional Safety Object: PSV-134 Tower Object: LT-101 Object Class: Device Object: XS-145 Object: XV-137 Object: PSV-134 Object .
method dispatch in different object-oriented programming languages. We also include an appendix on object-oriented programming languages, in which we consider the distinction between object-based and object-oriented programming languages and the evolution and notation and process of object-oriented analysis and design, start with Chapters 5 and 6;
TO KILL A MOCKINGBIRD. Contents Dedication Epigraph Part One Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Part Two Chapter 12 Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18. Chapter 19 Chapter 20 Chapter 21 Chapter 22 Chapter 23 Chapter 24 Chapter 25 Chapter 26
object-oriented programming language is based on a kind of old object-oriented programming language. For example, though C language is an object-oriented programming language, it still retains the pointer which is complex but has strong function. But C# improved this problem. C# is a kind of pure object-oriented language.
Reusability, CK Metric, Object - Oriented. 1. INTRODUCTION Object oriented systems continue to share a major portion of software development and customer base for these systems is on the rise. This is because there are many advantages in taking the object oriented concept. The weakness though is that most object oriented systems tend to be .
Object built-in type, 9 Object constructor, 32 Object.create() method, 70 Object.defineProperties() method, 43–44 Object.defineProperty() method, 39–41, 52 Object.freeze() method, 47, 61 Object.getOwnPropertyDescriptor() method, 44 Object.getPrototypeOf() method, 55 Object.isExtensible() method, 45, 46 Object.isFrozen() method, 47 Object.isSealed() method, 46
2.1 ASTM Standards:2 C186 Test Method for Heat of Hydration of Hydraulic Cement C1679 Practice for Measuring Hydration Kinetics of Hy-draulic Cementitious Mixtures Using Isothermal Calorim-etry E691 Practice for Conducting an Interlaboratory Study to Determine the Precision of a Test Method 3. Terminology 3.1 Definitions of Terms Specific to This Standard: 3.1.1 baseline, n—the time-series .
