\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Object Oriented Database Management Systems-Concepts, Advantages, Limitations and Comparative Study with Relational Database Management Systems By},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2015-01-15 (revised: 15 January 2015)}
\def\TheID{\makeatother }
\def\TheDate{2015-01-15}
\title{Object Oriented Database Management Systems-Concepts, Advantages, Limitations and Comparative Study with Relational Database Management Systems By}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Hardeep Singh  Damesha}

             \affil[1]{  Lovely Professional University}

\renewcommand\Authands{ and }

\date{\small \em Received: 16 December 2014 Accepted: 5 January 2015 Published: 15 January 2015}

\maketitle


\begin{abstract}
        


Object Oriented Databases stores data in the form of objects. An Object is something uniquely identifiable which models a real world entity and has got state and behaviour. In Object Oriented based Databases capabilities of Object based paradigm for Programming and databases are combined due remove the limitations of Relational databases and on the demand of some advanced applications. In this paper, need of Object database, approaches for Object database implementation, requirements for database to an Object database, Perspectives of Object database, architecture approaches for Object databases, the achievements and weakness of Object Databases and comparison with relational database are discussed.

\end{abstract}


\keywords{relational databases, object based databases, object and object data model.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 \par
I. Introduction istory of data processing goes through many different changes with different technologies along with the time. In decade there is huge increase in the volume of data that need to be processed due to which sometimes old technology do not work and need to come with new technology to process the data. History of database technology has used Unit Records \& Punch Card, Punch Card Proliferation, Paper Data Reels, \& Data Drums, File Systems, Database Systems, NoSQL and NewSQL databases. From last five decades, the mostly used technology is database management systems.\par
After some limitations of file systems, researchers come up with new technology known as Database Management Systems which is the collection of software or programs to maintain the data records. Initially, two models are proposed are hierarchical and network models, but these models don't get much popularity due to their complex nature. Then a researcher E.F. Codd comes up with a new data model known as relational model in which data items are stored in a table. Many DBMS's are developed on the basis of this model. This is the most popular model till now because it has conceptually foundation from relational mathematics.\par
In mid-1980's ,no doubt RDBMS are very much popular but due to some limitation of relation model and RDBMS do not support for some advanced applications \hyperref[b0]{[1]} OODB comes in the picture. At that time Object Oriented Programming paradigm is very much popular. Due to this researcher think to combine the capabilities of database and object based paradigm for programming. In Object databases data is stored in the forms of objects. These database management systems are not very much popular because due to the lack of standards.\par
Research is going on the database technology from 1960's up to this day. Many improvements are done in database technology by researcher in last decade and more technologies are coming to improve the database technology. The new database technologies include new transaction management and concurrency control methods and Redundant Array of Independent Disks (RAID) for efficient storage and Big Data and Cloud Computing. 
\section[{II. Why Object Oriented Databases?}]{II. Why Object Oriented Databases?}\par
There are three reasons for need of OODBMS: For this you must know:\par
? Depth of recursive query must be known.\par
? You can use the transitive closure operations to handle recursive queries in RDBMS. 9. Impedance mismatch: SQL Data Manipulation Language (DML) is lack computational completeness \hyperref[b8]{[10]}. To overcome this situation, you must embed the SQL with any high programming language like C++, Java, and C \#. Due to there will be impedance mismatch between two language SQL and higher programming language. 10. Poor support for long duration transactions: In RDBMS, generally transactions are short lived and concurrency control techniques or mechanisms are not good for .long duration transactions. 11. Poor Schema Evolution support: Schema Evolution means making changes to schema of database at runtime without interrupt the execution of the application. 12. Poor Navigational Access: There is very poor support for the navigational access in RDBMS.\par
There are some advanced applications need the database with deeper structural and functional foundation of capabilities that are not provided by conventional database \hyperref[b0]{[1]}. These applications are: 
\section[{B. Need for Advanced Applications a) Computer Aided Design (CAD):}]{B. Need for Advanced Applications a) Computer Aided Design (CAD):}\par
? In these types of applications, relevant data about buildings, airplanes and integrated circuit chips is stored and managed. In this type of applications, database design may be very large.\par
? Design in these types of applications is not static. This design is evolves through the times. Updates need to be propagated.  
\section[{C. Popularity of Object Oriented Paradigm}]{C. Popularity of Object Oriented Paradigm}\par
Another domain that enforces the development of OODBMS is popularity of object oriented programming paradigm \hyperref[b2]{[4]}, \hyperref[b3]{[5]}, \hyperref[b4]{[6]}, \hyperref[b5]{[7]}, \hyperref[b6]{[8]}   
\section[{IV. Oodbms Manifesto a) Mandatory Features}]{IV. Oodbms Manifesto a) Mandatory Features}\par
The OODBMS paradigm manifesto set the minimum fundamental directional basis for an OODBMS model \hyperref[b1]{[3]}, \hyperref[b2]{[4]},  {\ref [5, [8]}.These characteristics can be classified as mandatory and optional features:\par
1. Support for complex objects: A OODBMS must support for complex objects. Complex objects can be obtained by applying constructor on basic objects. 2. Object Identity: It is the unique identifier associated with every object in the system. It has following characteristics:\par
? It is generated by system.\par
? It is unique to that object in the entire system.\par
? It is used only by the system, not by the user.\par
? It is independent the state of the object. 3. Encapsulation: An OODBMS should enforce encapsulation through access objects only. 
\section[{Types or Classes:}]{Types or Classes:}\par
A OODBMS must support for one of them types or classes. 5. Inheritance and Hierarchies: A OODBMS must support for concept of super classes and subclasses. The types of heritance can be: ? Substitution ? Inclusion ? Constraint ? Specialization 6. 
\section[{VI. OODBMS Architectures Approaches}]{VI. OODBMS Architectures Approaches}\par
The basic theme of OODBMS is to add persistence to OOPL as they provide object orientation. The major difference is that here database needs to store data as well as methods \hyperref[b0]{[1]}. c) Database Server: In this approach, Client simply passes the request to the server, receives results and passes them to application. Most of database processing done at server .This approach is used mainly by RDBMS's. 
\section[{Client/Server}]{Client/Server}\par
VII. Achievements and Weaknesses of OODBMS a) Achievements 1. Support for User Defined data types: OODBs provides the facilities of defining new user defined data types and to maintain them \hyperref[b7]{[9]}. 
\section[{OODB's allow creating new type of relationships:}]{OODB's allow creating new type of relationships:}\par
OODBs allow creating a new type of relationship between objects is called inverse relationship (a binary relationship) \hyperref[b9]{[11]}.  \hyperref[b9]{[11]}. 9. No full-fledged facilities to implement complex objects: No doubt, object oriented databases provide some facilities to implement the concept of complex objects. But there is no full -fledged implementation of complex objects \hyperref[b9]{[11]}. 10. Interoperability between OODB and Object Oriented Systems: In Object Oriented Programming objects are transient in nature. To provide persistent to data, OODB and OO systems need to be interoperable. Many problems may arise during interoperable between OODB and OO systems \hyperref[b9]{[11]}. 11. Limited performance gains over RDBs Decrease in performance: Performance gains changes application to application. Applications that make the use of object identity concept having performance gains over RDBMS's. But application that requires bulk database loading and does not make use of OID then performance of OODBMS's is not good \hyperref[b7]{[9]}. 12. Some basic features are not present: Some basic features like triggers, meta data management \hyperref[b9]{[11]} and constraints such as UNIQUE and NULL \hyperref[b7]{[9]} not present in object databases.\par
VIII. Comparison of OODBMS and RDBMS 
\section[{IX. Summary and Conclusion}]{IX. Summary and Conclusion}\par
No doubt, relational databases are very popular and there are found everywhere. The object oriented database comes into action in mid-1985's to remove the limitations and to support some advanced database applications like CAD, CASE etc. Another point that provides the momentum to develop object based database is popularity of object based programming. So; researchers in the field of database think to combine the object oriented programming concepts with database to make powerful database management systems. Different approaches are adopted by industry to make the database with object oriented features. These approaches include relational extensions and pure object oriented are most popular to develop object oriented database systems. OODBMS's are made by many vendors by using different approaches. OODBMS's removes the limitations of RDBMS's, also provide support for advanced database application with some additional features. But due to the lack of standards, they do not get much popularity in the industry. Then after some time, some limitations are found in object oriented database management systems.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
to this, sometimes it becomes very difficult to find\\
out that which is going to model data or\\
relationship?\\
4. Poor support for integrity and enterprise constraints:\\
Constraints are very much needed for your\\
database have to be desired data. RDM supports\\
only limited number of constraints. The enterprise\\
constraints are those which are defined by industry\\
standards.\\
5. Homogeneous data structure: RDM requires\\
homogeneous data structures like:\\
? RDM assumes both horizontal and vertical\\
homogeneity.\\
? Relational mathematics algebra has only fixed\\
number of operations due to which Relational\\
Model operations cannot be extended.\\
6.\\
A. Limitation of RDBMS\\
B. Need for Advanced Applications\\
C. Popularity of Object Oriented Paradigm\\
A. Limitation of RDBMS\\
These limitations are in relational model. Due to\\
this these limitations are reflected to all RDBMS [2].\\
These limitations are:\\
1. Poor representation of real world entities: The\\
Relational model cannot represent real world in\\
proper way because it has only one semantic that is\\
table which can represent the real world entity in\\
proper way.\\
2. Normalization is necessary, but sometimes not\end{longtable} \par
  {\small\itshape [Note: useful: Normalization in RDBMS to maintain the consistency of the database, but some broken relations is not related to real world.3. Overloading of semantic structure: Relational DataModel has only one semantic structure for representing data and relationship that is table. Due]} 
\caption{\label{tab_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.40941566122545536\textwidth}P{0.4383723681097705\textwidth}P{0.0022119706647740715\textwidth}}
\tabcellsep \multicolumn{2}{l}{? Mapping to OO schema and queries to relational}\\
\tabcellsep ones.\tabcellsep \\
\tabcellsep \multicolumn{2}{l}{? The underlying relational storage manager is}\\
\tabcellsep ALLBASE/SQL.\tabcellsep \\
\tabcellsep C. Pure OODBMS\tabcellsep \\
\tabcellsep \multicolumn{2}{l}{These type OODB's systems are not much}\\
\tabcellsep \multicolumn{2}{l}{popular because lack of standards [9]. There is no}\\
\tabcellsep \multicolumn{2}{l}{single definition for a single concept. For Example: An}\\
Information Hiding: It is process of separates external properties of an object from its internal properties, which are hidden from external environment. These two concepts also related with abstraction. Importance: These two concepts support the facility that internal properties of an object to be changed without affecting applications that use it, provided external properties remain same. It also provides\tabcellsep \multicolumn{2}{l}{Object has many definitions, but in RDB there is a fixed standard for or single definition for each concept like table .Here defining some definitions which are mostly accepted but not standardize [2]. OODB Model: It is data model that capture semantics of objects suited in object based programming paradigm. ZDONIK and MAIER give a threshold model that an Object database must have following features:}\\
data independence. ? To provide fully implemented functionality of complex objects. ? Support for User/Abstract Defined Types, operators and functions for accessing. ? To provide functionality of Active Databases and Inferencing.\tabcellsep ? Database management, concurrency control etc. functionality like ? Facility of Object Identity (OID). ? Facility of encapsulation. ? Facility of complex objects. ? Inheritance not must but may useful.\tabcellsep transaction\\
? QUEL is the manipulation language in INGRES.\tabcellsep \tabcellsep \\
? POSTQUEL in POSTGRES :Most of QUEL\tabcellsep \tabcellsep \\
commands are included in POSTQUEL:\tabcellsep \multicolumn{2}{l}{OODBMS: It is system which contains application}\\
1. Time varying data (snapshots and historical\tabcellsep \multicolumn{2}{l}{programs which are used to manage all object oriented}\\
data)\tabcellsep \multicolumn{2}{l}{database activities like manipulation of objects.}\\
2. Iterative queries 3. Alerters, Triggers and Rules for Inferencing.\tabcellsep \multicolumn{2}{l}{Some Commercial OODBMS [9]: ? Gemstone OODBMS is developed by Gemstone}\\
B. Object/Relational DBMS\tabcellsep Systems Incorporation.\tabcellsep \\
These systems have relational and object based both features by the definition [1], [2]. They provide similar objectives as provided by the Relational Extension approach of RDBMS. In this approach, build an object layer on the top of relational system like Open ODB and ODAPTER. They are built on different applications. It has following features: HP during mid's 90 and aims to support for broad base Open ODB/ODAPTER: Open ODB is an ORDBMS from architectures like Query Server or Client/Server.\tabcellsep \multicolumn{2}{l}{? Objectivity/DB OODBMS is developed by ? Stick to relational model Objectivity Incorporation. ? Have to OO features like complex object and UDT ? Objectstore OODBMS is developed by Progress (User Defined Types). Software Corporation. Design techniques for relational extensions: In ? Ontos OODBMS is developed by Ontos mid-80's a researcher named Stonebraker in OODBMS Incorporation. field represent the design techniques in this field with ? Definition of new operations of so defined data ? Definition of new data types OODBMS should follow: different proposals for Extended Type System for an ? DB4O from Versant Corporation.}\\
Generalization: It is method to create a superclass is called generalization. Specialization: It is process of forming a sub class is ? Based on Iris DBMS ? Based on Client/Server architectures ? Both data and applications can be shared by the user applications. called specialization. ? Clients use Application Program Interface (API) to 9. Polymorphism: It means "many forms". It is dynamic access information. feature which executes at run time of program. It involves the concept of overriding and overloading ? OSQL is data manipulation language for Open\tabcellsep \multicolumn{2}{l}{because a real life situation can be model in best way by using object oriented programming. OO Programming Aspects: 1. Abstraction: It is process of finding important aspects of an entity and ignoring unimportant types. ? Implementation of access methods. ? Optimized query processing for the queries on new data types. Other Extensions in RDBMS: The different techniques are adopted by different DBMS to support to support OO features:}\\
{}[10]. ODB/ODAPTER.\tabcellsep \tabcellsep \\
? Open ODB uses relational techniques to support to\tabcellsep \tabcellsep \\
OO features.\tabcellsep \tabcellsep \end{longtable} \par
  {\small\itshape [Note: aspects such as implementation details. The properties comprise two things state and behaviour. A state is models through the attributes of object and behaviour is models through operations executed on data by object.Global Journal of C omp uter S cience and T echnology Volume XV Issue III Version I Year ( ) C 2. Object: 4. Attributes: These represent the current state of an object. They can be two types: ? Simple Attribute ? Complex Attribute 5. Object Identity (OID): It is the unique identifier associated with every object in the system. It has following characteristics: ? It is generated by system. ? It is unique to that object in the entire system. ? It is used only by the system, not by the user. ? It is independent the state of the object. 6. Methods and Messages: These implement the behaviour of an object and involve encapsulation. Message: It is a request or call to an object to execute the method that is defined by message. 7. Class: It is Container/Template/Blue-print for objects. Objects inside a class called instances. It comprises many definitions in many different situations. For example: A Class behaves like an object with its own class data and operations. 8. Inheritance: 10. Complex Objects: An object is called complex object if it contains many sub objects and it is viewed as single object. Example: Country. Because it contains many states and again states contains cities. 11. Relationships: It is basically an association between two things. These are represented through reference attributes, typically implemented through OID's. Types of binary relationships are: ? One to One relationship ? One to Many relationship ? Many to One relationship ? Many to Many relationship ? The different programming paradigm during the different decades: ? Due to this researchers think to combine OO Paradigm and DB. III. Approaches for OODBMS A. Relational Extension Based DBMS B. Object/Relational DBMS C. Pure OODBMS A. Relational Extension Based DBMS This is the first approach that is adopted by industry and academia towards the implementations of OODBMS is to extend the relational model to provide the OO features [1], [2]. The advantages of this approach are: ? Support for variable length "undefined" data values. Using this support, generalized user defined data types can be represented. Like Oracle supported RAW, LONG and LONGRAW (65535 bytes).Global Journal of C omp uter S cience and T echnology Volume XV Issue III Version I Year ( ) C ? ? Object Model is implemented by Object Manager.OODB:]} 
\caption{\label{tab_2}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
V. OODBMS Perspectives\\
a) Single Level Storage Model\\
Dynamic Binding: An OODBMS must support\\
concept of dynamic binding in programming\\
language such as:\\
? Overloading\\
? Overriding\\
? Late binding\\
7. Computationally Complete DML: To provide a\\
support for data processing database have use\\
computationally completely language like SQL-3.\\
8. Extensible set of data types: A OODBMS must\\
support for used defined data types.\\
9. Data Persistence: This is basic requirement for any\\
DBMS.A OODBMS must provide persistent by\\
storing object in proper way.\\
10. Managing very large databases: A OODBMS must\\
support for large databases.\\
11. Concurrent Users: This is basic requirement for any\\
DBMS. It must support for concurrency control.\\
12. Transaction Management: This is also basic\\
requirement of any DBMS.\\
13. Query Language: This is also a basic requirement of\\
any DBMS. This query language must be\\
computationally complete.\\
b) Optional Features\\
1. Multiple Inheritance: Multiple inheritance is not\\
directly support by multiple objects oriented\\
programming languages. An OODBMS can also\\
support for multiple inheritance.\\
2. Type checking and inferencing: Type Checking and\\
Inferencing features can be added to Object\\
Databases.\\
3. Long duration and Nested Transactions: Relational\\
database transactions are short-lived. An OODBMS\\
can support for .long duration transactions and also\\
for nested transactions.\\
4. Distributed databases: An object database may\\
have support for distributed database which is a\\
collection of multiple databases logically related\\
and distributed over the network.\\
5. Versions: An OODBMS can support for version\\
control and configuration management.\end{longtable} \par
 
\caption{\label{tab_3}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3} \par 
\begin{longtable}{P{0.85\textwidth}}
d) Weaknesses\\
1.\end{longtable} \par
  {\small\itshape [Note: the system\hyperref[b11]{[13]}.Optimization of queries is very important for performance gains. But due to following reasons it is difficult to optimize queries in object databases:?User defined data types ? Changing variety of types ? Complex objects, methods and encapsulation ? Object Query language has nested structure ? Object Identity 3. No fixed query algebra for OODBMS's: Due to lack of the standards in OODBMS, there is no standard query algebra for OODB. Lack of standard query algebra becomes one of the reasons for problem of query optimization. There are different query languages for different object databases. 4. No full-fledged query system: Query system also not fully implemented. Some query facilities lacks in Object databases like nested sub-queries, set queries and aggregation function [9], [11]. 5. No facility for Views: In relational databases, views are temporary tables. Object databases having no facility for views. An object oriented view capability is difficult to implement due to the features of Object Model such as object identity. Object oriented programming concepts like inheritance and encapsulation makes the difficult to implement views in object databases [11]. 6. Security problems in Object databases: Security is related to authentication, authorization and accounting. Discretionary Access Control (DAC), Mandatory Access Control (MAC) security policies are implemented in object databases to secure data. In some systems provide security on the basis of object oriented concepts like encapsulation.Object database having to facilities for authorization\hyperref[b7]{[9]}.7.No support for schema evolution with OODBs:]} 
\caption{\label{tab_4}3 .}\end{figure}
 			\footnote{© 2015 Global Journals Inc. (US) 1} 			\footnote{© 2015 Global Journals Inc. (US)} 		 		\backmatter   			 
\subsection[{Acknowledgement}]{Acknowledgement}\par
The Author would like to special thanks Sardar Chet Singh Damesha, Sardarni Sachiar Kaur Damesha and whole Damesha family for inspiring me everytime and always with me. 			  			  				\begin{bibitemlist}{1}
\bibitem[Kim (ed.) (1988)]{b4}\label{b4} 	 		\textit{A foundation for object-oriented databases},  		 			W Kim 		.  		MCC Tech. Rep., N.ACA-ST-248-88 (ed.)  		Aug. 1988.  	 
\bibitem[Scholl and Schek ()]{b10}\label{b10} 	 		‘A relational object model’.  		 			M Scholl 		,  		 			H Schek 		.  	 	 		\textit{Proc. 3rd Int. Conf. On Database Theory},  		Lecture Notes in Computer Science  		 			S Abiteboul,  			P C Kanellakis 		 (ed.)  		 (3rd Int. Conf. On Database Theory)  		1990. Springer Verlag. 470 p. .  	 
\bibitem[Bancilhon ()]{b3}\label{b3} 	 		‘Object Oriented database systems’.  		 			F Bancilhon 		.  	 	 		\textit{Proc. 7th ACM SIGART/SIGMOD Conf},  				 (7th ACM SIGART/SIGMOD Conf)  		1988.  	 
\bibitem[Object Oriented Database Systems: Approaches and Architectures by C.S.R. Prabhu 2. Database System: A Practical Approach to Design, Implementation and Management by T. Connoly and C. Begg]{b0}\label{b0} 	 		\textit{Object Oriented Database Systems: Approaches and Architectures by C.S.R. Prabhu 2. Database System: A Practical Approach to Design, Implementation and Management by T. Connoly and C. Begg},  		 	 	 (Research Papers) 
\bibitem[Kim and Kim ()]{b7}\label{b7} 	 		‘Object-Oriented Database Systems: Promises, Reality, and Future’.  		 			W Kim 		,  		 			W Kim 		.  	 	 		\textit{Modern Database Systems: The Object Model, Interoperability and Beyond},  				1995. Addison Wesley. p. .  	 
\bibitem[Stefik and Bobrow (1986)]{b5}\label{b5} 	 		‘Object-oriented programming: Themes and variations’.  		 			M Stefik 		,  		 			D Bobrow 		.  	 	 		\textit{The AI Mag}  		Jan 1986.  	 
\bibitem[Bertino et al. ()]{b8}\label{b8} 	 		‘Object-Oriented Query Languages: The Notion and the Issues’.  		 			E Bertino 		,  		 			M Negri 		,  		 			G Pelagatti 		,  		 			L Sbattella 		.  	 	 		\textit{IEEE Transactions on Knowledge and Data Engineering}  		1992. 4  (3) .  	 
\bibitem[Erlingsson]{b11}\label{b11} 	 		\textit{Object-Oriented Query Optimization},  		 			U Erlingsson 		.  		 	 	 (unpublished manuscript) 
\bibitem[Zdonik and Maier ()]{b6}\label{b6} 	 		\textit{Readings in Object-Oriented Database Systems},  		 			S B Zdonik 		,  		 			D Maier 		.  		1989. San Mateo, CA: Morgan Kauffman.  	 
\bibitem[Atkinson et al. (1989)]{b1}\label{b1} 	 		\textit{The Object Oriented Database Manifesto},  		 			M Atkinson 		,  		 			F Bancilhon 		,  		 			D Dewitt 		,  		 			K Dittrich 		,  		 			D Maier 		,  		 			S Zdonik 		.  		December 1989.  	 
\bibitem[Atkinson ()]{b2}\label{b2} 	 		‘The object-oriented database system manifesto’.  		 			M Atkinson 		.  	 	 		\textit{Proc. Int. Conf. On Deductive and Object-Oriented Databases},  				 (Int. Conf. On Deductive and Object-Oriented Databases)  		1989.  	 
\bibitem[Dittrich and Dittrich ()]{b9}\label{b9} 	 		‘Where Object-Oriented DBMSs Should Do Better: A Critique Based on Early Experiences’.  		 			K A Dittrich 		,  		 			K R Dittrich 		.  	 	 		\textit{Modern Database Systems: The Object Model, Interoperability and Beyond},  				 (Kim, W.)  		1995. Addison Wesley. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
