What is it? And how it
works?
Well, after searching and asking to get a
simplest definition of “object oriented databases” I can say that it is a
database that has the ability to take “inputs” and reflect them into “outputs”,
all of which dealing with specified objects, and following specific “methods”. A
programmable language designs this database. The data restored on the database
have the form of “objects”. And how it works is that we have objects stored on
the database that reference the ability to develop a product, which can be
saved and stored again as a new assembled object. This new object can be
recalled later easily without reassembling it again.
Relation to “relational
databases”:
OODB differs than the relational database
by the following. Relational database deals with tables filled with integers,
character strings and simple text facts; whereas OODB designed to work with
images, videos and 3d objects. In addition, RDB organizes data in tables that
are already installed and stored, while OODB has the ability to develop new
products based on the stored objects and data. However, RDB is easy to use for
non-specialized users and can be programed by non-expert users; whereas OODB
requires special kind of programming language and a little bit not user
friendly.
Is it the best database?
To answer this question properly, we
need to know the purpose of the desired database. For example, if we want a
database for an eLibrary, then the best choice here is relational database
since it is very easy to use and to design and we don’t need to store complex
objects in the database. However, in BIM world, object oriented database is
much better than relational database. The reason behind this is that we are
going to be dealing with objects and these objects are to be modified and
retrofitted then defining new objects based on the reference objects we have.
Also, we can recall the objects created at anytime easily without creating them
again.
Comments:
Lewis:
I like your point of interest where you
are addressing the advantages of object oriented database and also saying that
it is not beneficial or efficient to have this kind of database for a simple
set of data. Also, I agree with you pointing out that OODB works best for CAS
and products that change over time, since relational database doesn’t have the
ability to edit the data stored, whereas OODB is more flexible.
Yau:
It is very interesting that you mentioned
the hybridize both relational and object oriented databases to get the most
efficient and beneficial database type. However, I didn’t get how OODB doesn’t
have the ability to adapt changes in variables; and I do agree that the
reliance of OODB on a single programming language is a disadvantage.
Perdue:
I liked the idea of how databases can aid
the contractors in construction fields by using databases with advanced
time-lapse video technology built in the database; I assume that this kind of
database is the OODB. It is really great to have that kind of aiding tool to
help contactors, designers and engineers to communicate, comment and adjust
what is needed on the building at the same time.
Resources:
No comments:
Post a Comment