CS35A: Group Assignment One

1
CS35A Group Assignment One

• Object-Relational Models

2
Group Six Members

• Garfield King
• Vinesha Anderson
• Andrae Marsh
• Roxanne Reynolds
• Jody-Ann Wright
• Omar Annakie

3
Introduction

• Database Modeling
• This is a plan for building a database, which
  describes the overall structure of a database.
• Organizations process large amounts of data in
  their daily processes.
• Proper management, effective processing and use
  of this data is essential for all types of
  organizations.
• Nowadays organizations are confronted with new
  data management requirements.
• Hence the need for new Data Models

4
Evolution of Database Management Systems

• 1st Generation
• Hierarchical
• Network
• 2nd Generation
• Relational Database
• 3rd Generation
• Object Oriented Database
• Object-Relational Database

5
What is the Object-Relational Data Model?

• Extension of the relational data model
  incorporating object orientation constructs.
• Defines an object layer that sits atop a
  conventional tabular relational engine.
• Allows developers to integrate the database with
  their own custom data types and methods
  (classes).

6
What is the Object-Relational Data Model?

• Support for diverse binary media such as audio,
  video, images, and applets.

7
Graphic overview of Object-Relational Model

• Borrows features from both relational and object
  data model
• Data manipulation and definition from Relational
  model.
• Operators for complex data types, inheritance and
  polymorphism, etc. from the Object Oriented data
  model.

8
Features of Object Relational Data Model

• Support for
• User-defined types
• Complex data types
• User-defined functions
• Operators
• Inheritance
• Encapsulation
• Polymorphism
• Object storage capabilities to the relational
  systems.
• These new facilities integrate management of
  traditional fielded data as well as complex
  objects.

9
Features Continued

• Simplify data modeling and querying by using
  complex data types.
• Allows attributes of tuples to have complex
  types, including non-atomic values such as nested
  relations.
• Incorporates both data and processes

10
Applications of Object-Relational Data Model

• When your application processes a large number of
  short-lived transactions (e.g. ad-hoc queries) on
  complex data items
• Multimedia databases.
• Frequently used in web applications and
  specialized data warehouses.

11
Sample Application

• Multimedia databases

12
Sample Application

• Computer Aided Design (CAD).
• Possible due to the ability to implement
  powerful user defined types

13
(No Transcript)
14
Applications Continued.

• Managing media objects and complex data such as
  financial times series and geographic data.

15
Sample Application

• Modeling of complex objects.

16
Advantages of the Object-Relational Model

• Provides all the traditional advantages of the
  relational data model, while resolving known
  weaknesses of the model.
• Preserves significant body of knowledge and
  experience gone into developing relational
  applications.
• Reuse and sharing
• Reuse from ability to extend server to perform
  standard functionality centrally.
• increased productivity for developer and end-user.

17
Advantages Continued

• Allows developers to integrate the database with
  their own custom data types and methods.
• Supports complex objects, such as time-series,
  geospatial data and diverse binary media.
• Provides logical independence of data from
  application.

18
Advantages Continued

• Object-Relational migration will not necessarily
  entail wholesale recoding
• Preserve relational foundations, while extending
  modeling power.
• Provide good protection of data from programming
  errors and makes high level optimizations.

19
Advantages Continued

• Execute complex analytical and data manipulation
  operations to search and transform multimedia and
  other complex objects.
• Upward compatibility with existing relational
  languages.

20
Disadvantages of ORDBMS

• Being a new technology it is limited to mostly
  new data types.
• Immature extensions are new, are still being
  defined, and are relatively unproven.
• Complexity. Because of the complex data
  relationships it is difficult to model.

21
Disadvantages of ORDBMS

• Increased costs.
• Proponents of relational approach believe
  simplicity and purity of relational model are
  lost.
• Lacks the fundamental object requirement of
  encapsulation of operations with data.
• SQL now extremely complex.

22
Comparison of ORDBMS and OODBMS

• Language Dependence
• Lack of Ad-Hoc Queries
• OODBMS provides weaker support for production
  features such as back up and recovery than its OR
  counterpart.
• Schema Changes

23
Example of Object-Relational DBMS

• Proprietary Software
• DB2
• GigaBASE
• Oracle
• UniSQL
• Sybase
• PostgreSQL (Free Software)
• Inter Systems Cache
• Informix Universal Server on Unix, NT, and
  Windows platforms.

24
Examples Continued Informix

• Informix IUS relational features include
• SQL
• Views
• Security
• Transactions
• Backup and recovery
• Informix object-oriented features include
• User-defined types
• User-defined functions
• Unique object identifiers (OIDs)
• Inheritance
• Polymorphism

25
Modeling Tools

• DBMS-independent tools with ORDBMS capabilities
• OR Compass from Logic Works Inc.
• InfoModeler 3.1 from InfoModelers Inc.
• Universal Modeler 1.0 from Silverrun Technologies
  Inc.
• Platinums ParadigmPlus, etc
• Each tool lets you specify physical database
  properties (spacing, locking mode) of tables and
  other database objects.
• They generate physical schemas, either directly
  to the database or, with the exception of
  InfoModeler, in data-definiton language files.

26
Conclusion

• Inherited the robust transaction and
  performance-management features of its relational
  ancestor and the flexibility of its
  object-oriented cousin.
• Database designers can work with familiar tabular
  structures and data definition languages (DDLs)
  while assimilating new object-management
  possibilities.