17
Graduate Presentation April13 2011 By Sai Silpa Surapaneni

OODBMS Presentation

Embed Size (px)

Citation preview

Page 1: OODBMS Presentation

Graduate Presentation April13 2011

BySai Silpa Surapaneni

Page 2: OODBMS Presentation

1. Introduction

2. Object oriented database.

3. How is it different from Relational Database?

4. Use of object oriented databases

5. Object oriented databases Vs Relation databases

6. Advantages

7. Disadvantages

8. Summary

Page 3: OODBMS Presentation

Database is designed in order to store any type of data , that may be simple data(like just text, numerics), complex data.

Complex data???What is this?? A lack of unique, natural identification. A large number of many-to-many

relationships.

Page 4: OODBMS Presentation

For e.g., In computer aided design application in which the user can save and load complex engineering drawings into memory.

So this data can easily be retrieved when we use “Object Oriented Databases”

We can now classify that Database Used to retrieve Relational Database simple data Object oriented Database Complex data

Page 5: OODBMS Presentation

Defined to be one in which data and the actions that operate on the data are encapsulated into objects.

Objects are nothing but which exists in real world.

Something like , let us relate to our very known premiere database

CUSTOMER,PART,ORDERS,ORDER_LINE– these are objects.

Page 6: OODBMS Presentation

Class:A class is a blueprint or prototype from which objects

are created.

Attributes: Attributes are data which defines the characteristics of

an object.

Methods:Methods are the actions defined for a class.

Inheritance:

For any class there can be a sub class. The subclass inherits the structure of the class as well as its methods. In addition you can define additional attributes and methods for the subclass

Page 7: OODBMS Presentation
Page 8: OODBMS Presentation

CAS Applications (CASE-computer aided software engineering, CAD-computer aided design, CAM-computer aided manufacture)

Multimedia Applications Commerce

OBJECT ORIENTED DATABASES SHOULD NOT BE USED WITH:

When there would be few join tables. There are large volumes of simple

transactional data.

Page 9: OODBMS Presentation

Relational Database uses SQL(Structured Query Language)

Object Oriented database uses OQL(Object Query Language)

(syntax is based on SQL)

Consider a table:Student ID Student

nameDepartment

1201 John Computers

1202 Smith Arts

1203 Jim Arts

Page 10: OODBMS Presentation

Execute the Query What are the names of Art department

students?

SQL will result as OQL will result as

Returns a table with rows Returns a collection of objectsStudent name

Smith

Jim

String

Smith

String

Jim

QUERY RETURNS

OQL SQL

object Tuple

Collection of objects Table

Page 11: OODBMS Presentation

Abstraction: Class definition, provides extension to complex attribute types

Encapsulation: Implementation of operations and object structure hidden

Polymorphism: Polymorphism is the ability of objects belonging to different classes to perform the same operation differently.

Page 12: OODBMS Presentation

This system is based on a table structure that stores and manages data

Uses normalization concept to reduce redundancy of data

Loads entire table into memory irrespective of the tuple needed in the query.

Uses SQL Better Performance in

handling simple data Persistence of data is

not guaranteed.

Data is defined as an objects and classes

Uses Object oriented concepts such as inheritance and encapsulation to establish relations between classes.

Creates memory only to necessary objects.

Uses OQL Better Performance in

handling complex data Persistence is

guaranteed.

Page 13: OODBMS Presentation

Designer can specify the structure of objects and their behavior (methods)

Better interaction with object-oriented languages such as Java and C++

Definition of complex and user-defined types

Encapsulation of operations and user-defined methods

Page 14: OODBMS Presentation

Lower efficiency when data is simple and relationships are simple.

Relational tables are simpler. More user tools exist for RDBMS. Standards for RDBMS are more stable. Support for RDBMS is more certain and

change is less likely to be required.

Page 15: OODBMS Presentation

There is no real right or wrong answer to this question.

The choice made is based on the data to be stored/managed, the type of database needed and the technology preferences of the company providing the service or company who is receiving the service.

Page 16: OODBMS Presentation

OODBMS depends on object orientation. It is used when complex data has to be

stored and retrieved like multimedia objects. It uses OQL(Object Query Language). It is mainly used in the fields of CAD/CAM. Unlike the RDBMS it consumes less memory

by loading only necessary objects. It is not suitable for large volumes of simple

data Hence OODBMS is said to be a best

database in case of complex data handling.

Page 17: OODBMS Presentation

SAI SILPA SURAPANENI