0% found this document useful (0 votes)
133 views

OODBMS Presentation

This document summarizes a graduate presentation by Sai Silpa Surapaneni on object-oriented databases. It discusses how object-oriented databases differ from relational databases in storing complex data as objects rather than tables. Key features of object-oriented databases include encapsulation, inheritance, and polymorphism. Object-oriented databases are best suited for applications involving complex data like CAD/CAM, while relational databases are more efficient for large volumes of simple transactional data.
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
133 views

OODBMS Presentation

This document summarizes a graduate presentation by Sai Silpa Surapaneni on object-oriented databases. It discusses how object-oriented databases differ from relational databases in storing complex data as objects rather than tables. Key features of object-oriented databases include encapsulation, inheritance, and polymorphism. Object-oriented databases are best suited for applications involving complex data like CAD/CAM, while relational databases are more efficient for large volumes of simple transactional data.
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

Graduate Presentation

April13 2011

By
Sai Silpa Surapaneni
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
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.
 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
 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.
 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
 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.
 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 name Department
1201 John Computers
1202 Smith Arts
1203 Jim Arts
 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 objects
Student name String String
Smith Jim
Smith
Jim

QUERY RETURNS
OQL SQL
object Tuple
Collection of objects Table
 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.
 This system is based on a  Data is defined as an
table structure that stores objects and classes
and manages data  Uses Object oriented
 Uses normalization concepts such as
concept to reduce inheritance and
redundancy of data encapsulation to establish
 Loads entire table into relations between classes.
memory irrespective of  Creates memory only to
the tuple needed in the necessary objects.
query.  Uses OQL
 Uses SQL  Better Performance in
 Better Performance in handling complex data
handling simple data  Persistence is guaranteed.
 Persistence of data is not
guaranteed.
 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
 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.
 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.
 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.
SAI SILPA SURAPANENI

You might also like