\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={Evolution of Object-Oriented Database Systems},
 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{2016-01-15 (revised: 15 January 2016)}
\def\TheID{\makeatother }
\def\TheDate{2016-01-15}
\title{Evolution of Object-Oriented Database Systems}
\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]{Hibatullah  Alzahrani}

             \affil[1]{  Clark Atlanta University}

\renewcommand\Authands{ and }

\date{\small \em Received: 12 December 2015 Accepted: 3 January 2016 Published: 15 January 2016}

\maketitle


\begin{abstract}
        


Data bases  are quintessential part of most modern web and mobile applications. In most part, relational databases dominate the database market but the evolution of object-oriented databases has provided users and developers with an alternative option. Object-oriented databases provide a number of advantages over relational databases like ease of extensibility, custom data models, provision for modelling complex data structures and faster access time. But they do lack in certain areas and have no strict standards and implementation mostly depends upon the vendor. Nevertheless, object-oriented databases are slowly finding their way into database market, especially in the area of large-scale databases. But the long history of relational databases keeps them alive as tough competitor and the future seems to be going towards object-relational databases.

\end{abstract}


\keywords{object-oriented, database, relational, data- base management system, evolution, advantages, disadvantages.}

\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& 	 	 		 
\section[{Introduction}]{Introduction}\par
atabases are the nuts and bolts of the modern information systems. Every major application on Internet and smartphones uses them in one way or another. They are ubiquitously used in data centers and for maintaining records in hospitals, universities and all kinds of government and private institutions. Strictly speaking, there is a distinction between a database and a database management system (DBMS) -database is an organized collection of data whereas DBMS is a software which interacts with the database and the user and acts as an interface between them. But usually database is used to refer to both the database itself and the DBMS. Most commonly used DBMS is Relational DBMS (RDBMS) which is based on relational data model in which data is stored as tables or "relations" consisting of rows and columns. With the advent of object-oriented programming paradigm and the rise of object-oriented programming languages, the concept of object-oriented databases was conceived in which data is represented as objects rather than as tables. Figure \hyperref[fig_0]{1} provides a mapping between the relational and objectoriented database model. In this article, we will briefly discuss what object-oriented databases are, trace the evolution of object-oriented databases, their use in modern systems and their advantages and disadvantages over traditional Relational Databases.\par
Author: e-mail: mesfer66@gmail.com Object-oriented databases are designed and built according to the object-oriented paradigm in which everything is modeled as objects including the data. This type of data model helps in tackling complex data structures, for instance multimedia content, in a more natural way and provides a seamless transition from design to conception. According to object-oriented database system manifesto \hyperref[b0]{[1]}, an Object-Oriented Database Management System (OODBMS) must satisfy two criterion: i) It should be a Database Management System (DBMS) ii) It should be an object-oriented system\par
The first criterion means that the OODBMS should provide the five features which are must for any database system -persistence, concurrency, data recovery, secondary storage management and ad hoc query facility. The second criterion means that the database system should support all the requisite features of an object-oriented system like encapsulation, complex objects, inheritance, polymorphism, extensibility etc. Hence the data in OODBMS is represented as collection of interacting objects instead of collection of inter-related tables. Usage of object-oriented concepts like polymorphism and inheritance make the interaction between the objects a trivial task. Figure \hyperref[fig_1]{2} provides an example of how the same data, customer account information for a banking system, is represented in two different formats. Whereas data is stored as tables in the relational database and we need to relate of "join" tables to perform a query, it is stored as a collection of objects in object-oriented database, and query can be easily performed by following the pointer from parent object to its children.  
\section[{Evolution of Object-Oriented Databases}]{Evolution of Object-Oriented Databases}\par
The term "object-oriented database system" was first introduced in 1985 in \hyperref[b1]{[2]} and \hyperref[b2]{[3]}. Orion Research Project at MCC headed by Won Kim was the first major project initiated for the development of OODBMS and several papers were published during its course, best of which were compiled by Won Kim in the form of book \hyperref[b3]{[4]} in 1990. Meanwhile Servo-Logic \hyperref[b4]{[5]} began work on one of the first commercial projects which was later renamed as Gem Stone [6] in 1995 and was based on Small Talk object-oriented language. Another Lisp-based system, Graphael, was introduced at around the same time in France and it was followed by O2 [7] in 1992 which was later acquired by IBM. Tom Atwood at Onto logic produced V base which later became ONTOS and was the first to support C++. Drew Wade at same time produced Objectivity/DB \hyperref[b6]{[8]},  {\ref [9]}. In 1989, first OODBS manifesto \hyperref[b0]{[1]} was published by Malcolm Atkinson which criticized relational model for being inadequate in meeting the demands of new applications and laid down the criterion for the objectoriented database system. A year later, second manifesto \hyperref[b7]{[10]} was published, which went the opposite way by supporting relational model and wanting to support SQL for OODBS. The third and final manifesto was published in 1995 \hyperref[b8]{[11]} and it presented OO model as an extension of relational model and proposed to extend the relational model to incorporate the objectoriented characteristics by allowing for custom userdefined data types.\par
Meanwhile, work on standardization of OODBMS began in 1991 when Rick Cattell of Sun Microsystems formed a consortium of 5 major OODBMS vendors, named ODMG (Object Database Management Group). As a result of these efforts for standardization, standards were published for ODL (Object Definition Language), OQL (Object Query Language) and OML (Object Manipulation Language). First standard was released in 1993 \hyperref[b9]{[12]}, which was mostly designed with C++ in mind as primary object-oriented language but in the final release 3.0 in 2001 \hyperref[b10]{[13]}, Java bindings were added to the standard to support Java and later bindings for Small Talk were also added. Afterwards, the ODMG was disbanded. Meanwhile, some objectoriented features were also included in SQL: 1999 \hyperref[b11]{[14]} and were then revised in its 2003 version and then in the latest 2011 version \hyperref[b12]{[15]}. SQL: 2011 supports Object Language Bindings (SQL/OLB) for performing queries to Object-oriented databases and various other object oriented features.\par
In 2004, db4o \hyperref[b13]{[16]} was released as the first free open-source OODBMS and it was the first DBMS to implement native queries in the programming language itself like Java and C\#. Also Perst and DTS/S1 were made available under dual open-source and commercial licenses. In 2005, Microsoft implemented Native Queries in its .NET framework by introducing LINQ and DLINQ. As a result, many object-oriented languages now support native queries. Though this is not the same as a full-fledge open-source database system, but it does provide the user or developer with an alternative option other than commercial databases, important since commercial OO databases are usually costlier than relational ones. 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
Volume XVI Issue III Version I  
\section[{Advantages of oo Databases}]{Advantages of oo Databases}\par
Since Relational Databases have been the norm of the day for a long period of time, any new emerging technology is compared against this benchmark to measure its usefulness. Some of the advantages of OODBMS over traditional RDBMS are: a) Complex Data Models\par
In relational databases, all data is modeled as relations or tables and it is extremely complicated to model complex data structures. Object-oriented databases model all data as objects which can model even complex data structures very easily. In fact, one of the very first application for object-oriented databases were graph-based data structures which were modelled easily using object-oriented concepts but were a nightmare to model in relational databases. 
\section[{b) Real-World Modelling}]{b) Real-World Modelling}\par
One of the strengths of object-oriented paradigm is its ability to model the real-world objects in a natural way. This becomes useful in maintaining data when we can store it as an object rather than a table and then perform manipulations on it. For instance, a very important application of OO databases is maintaining multimedia content. While using relational databases, it is cumbersome to store this content in form of tables but OO database can model the whole multimedia document as an object and store it easily. c) Extensibility (Provision of New Custom Data Types)\par
OO databases provides the ability to form new data types from existing ones using the object-oriented concepts of inheritance and polymorphism. No such feature is available in relational databases. 
\section[{d) No Impedance Mismatch}]{d) No Impedance Mismatch}\par
In OODBMS, there is no mismatch between data represented by database system and the data representation required by application. We can model our data as required by the application and subsequently use it directly in our application. This is in contrast to RDBMS in which all data has to be stored in form of tables and then at runtime, data is manipulated into the form required by the application. e) Ease of Design and Implementation Relational Data Models are not very descriptive in nature and in general, the database is first designed using Entity Relationship (ER) model and then implemented using relational model. Object-oriented databases do away with this hassle by designing the data directly as objects and then implementing it as such.\par
f) Faster Data Access and Improved Performance OODBMS are usually much faster than relational ones since they have a many-to-many relationship and objects can be accessed using pointers only. Furthermore, there is no need for 'join' as objects are linked through pointers and any specific object can be found following the chain of pointers. g) Easy handling of very large data Object-oriented databases can very easily handle very large amounts of complex data and as a result, very large databases are often built using OODBMS. In fact, world's largest database is an OODBMS -Stanford Linear Accelerator Center (SLAC) BaBar database  {\ref [17]} uses Objectivity/DB [9] and currently sizes almost 900 TB.\par
IV. 
\section[{Disadvantages of oo Databases}]{Disadvantages of oo Databases}\par
Despite all its advantages, OODBMS are still not as popular as relational databases due to following reasons: a) No Universal Data Model Relational databases have a fixed data model in which data is always represented in the form of tables. No such standard exists for object-oriented databases in which data is modeled as custom objects and depends on the type of data and need of application. 
\section[{b) No Standard Query Language}]{b) No Standard Query Language}\par
There is no standard query language for OODBMS like SQL for Relational Databases. Even though ODMG standardized OQL (Object Query Language) but it is still widely unimplemented. More recently, trend has been towards implementing Native Queries in programming languages like LINQ in C\# or the database vendor provides separate bindings for most popular object-oriented languages like Java, C++ etc. 
\section[{c) No Mathematical Foundation}]{c) No Mathematical Foundation}\par
Relational Databases are based on the solid foundations of Relational Algebra and Relational Calculus. No such mathematical foundation exists for object-oriented databases. d) Lack of Ad hoc Queries or Closure Closure is a property of relational databases which enables nested queries where new tables are created by joining existing ones and then querying the new table. Since there are no joins in OODBMS, there are no nested queries and the nature of query that can be performed is highly dependent on the design of database. Hence strictly speaking, some OODBMS can violate an essential criterion for database management systems which requires that all database management system should support ad hoc query.\par
V. 
\section[{Conclusion}]{Conclusion}\par
Object-oriented databases have been around for quite some time now but they haven't found widespread acceptance like relational databases. They \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}DFigure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_3}Global}\end{figure}
 			\footnote{© 2016 Global Journals Inc. (US)} 			\footnote{© 2016 Global Journals Inc. (US) 1} 			\footnote{© 2016 Global Journals Inc. (US) Evolution of Object-Oriented Database Systems} 		 		\backmatter  			 \par
data structures. But still, they are not as ubiquitous as relational databases. The present trend is towards incorporating the good features of both types of databases forming a hybrid one, called Object-Relational Database, which is intrinsically a relational database with object-oriented features. Even the modern standards of SQL provide some object-oriented features. Thus integration of object-oriented features in relational databases highlight their importance and the competition they pose. Already, very big databases are being designed using object-oriented paradigm and as databases become larger and larger, it is inevitable that the trend would go towards object-oriented databases in future.			 			  				\begin{bibitemlist}{1}
\bibitem[Melton]{b11}\label{b11} 	 		\textit{Advanced SQL, 1999: Understanding Object-Relational and Other Advanced Features},  		 			Jim Melton 		.  		 	 
\bibitem[Atwood (1985)]{b1}\label{b1} 	 		‘An Object-Oriented DBMS for Design Support Applications’.  		 			T Atwood 		.  	 	 		\textit{Proceedings of the IEEE COMPINT}  		September 1985. 85 p. .  	 
\bibitem[Delobel and Kanellakis ()]{b5}\label{b5} 	 		\textit{Building an Object-Oriented Database System: The Story of O 2},  		 			Claude ; Delobel 		,  		 			Paris Kanellakis 		.  		1992. Morgan Kaufmann Publishers.  	 
\bibitem[Guess (2013)]{b6}\label{b6} 	 		 			Angela Guess 		.  		\textit{Objectivity Launches Objectivity/DB 11.0". DATAVERSITY. Retrieved},  				February 6. 2013. December 2, 2014.  	 
\bibitem[Kim ()]{b3}\label{b3} 	 		\textit{Introduction to Object-Oriented Databases},  		 			Won Kim 		.  		1990. The MIT Press.  	 
\bibitem[Maier et al. (1985)]{b4}\label{b4} 	 		‘Object-Oriented Database Development at Servio Logic’.  		 			D Maier 		,  		 			A Otis 		,  		 			A Purdy 		.  	 	 		\textit{Database Engineering}  		December 1985. 18  (4) .  	 
\bibitem[Derrett et al. (1985)]{b2}\label{b2} 	 		‘Some Aspects of Operations in an Object-Oriented Database’.  		 			N Derrett 		,  		 			W Kent 		,  		 			P Lyngbaek 		.  	 	 		\textit{Database Engineering}  		December 1985. IEEE Computer Society. 8  (4) .  	 
\bibitem[The Committee for Advanced DBMS Function, Third Generation Database System Manifesto Computer Standards and Interfaces ()]{b7}\label{b7} 	 		‘The Committee for Advanced DBMS Function, Third Generation Database System Manifesto’.  	 	 		\textit{Computer Standards and Interfaces},  				1991. North Holland. 13 p. .  	 
\bibitem[Edlich et al. ()]{b13}\label{b13} 	 		\textit{The definitive guide to db4o},  		 			Stefan Edlich 		,  		 			Jim Paterson 		,  		 			Henrik Hörning 		,  		 			Reidar Hörning 		.  		2004. Apress.  	 
\bibitem[Cattell and Barry (ed.) ()]{b10}\label{b10} 	 		\textit{The Object Data},  		 			R G G Cattell 		,  		 			Douglas K Barry 		.  		 Standard: ODMG 3.0.  		Mark Berler, Jeff Eastman, David Jordan, Craig L. Russell, Olaf Schadow, Torsten Stanienda, and Fernando Velez (ed.)  		2000. Morgan Kaufmann Publishers, Inc.  	 
\bibitem[
			RG G
		 ()]{b9}\label{b9} 	 		\textit{The Object Database Standard: ODMG-93, Release 1.1 The Morgan Kaufmann Series in Data Management Systems},  		 			RG G 		.  		1994.  	 	 (Cattell (ED)) 
\bibitem[Atkinson et al. (1989)]{b0}\label{b0} 	 		‘The Object-Oriented Database System Manifesto’.  		 			M Atkinson 		,  		 			F Bancilhon 		,  		 			D Dewitt 		,  		 			K Dittrich 		,  		 			D Maier 		,  		 			S Zdonik 		.  	 	 		\textit{Proc. of the First International Conference on Deductive and Object-Oriented Databases},  				 (of the First International Conference on Deductive and Object-Oriented DatabasesKyoto, Japan)  		December 1989. p. .  	 
\bibitem[Darwen and Date (1995)]{b8}\label{b8} 	 		‘The Third Manifesto’.  		 			H Darwen 		,  		 			C J Date 		.  	 	 		\textit{SIGMOD RECORD}  		March 1995. 24  (1)  p. .  	 
\bibitem[Zemke ()]{b12}\label{b12} 	 		‘What's new in SQL’.  		 			Fred Zemke 		.  	 	 		\textit{ACM SIGMOD Record}  		2011. 2012. 41  (1)  p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
