Databases
cancel
Showing results for 
Search instead for 
Did you mean: 

OODB V.S Relational DB (e.g. Oracle)

SOLVED
Go to solution
Chris Fung
Frequent Advisor

OODB V.S Relational DB (e.g. Oracle)

Hi everyone,

Any idea for the topic. Just want to get come comparison and usage between them.

10 points will be given to your contribution. Web links are also appreciated.

Cheers,

Chris,

6 REPLIES
T G Manikandan
Honored Contributor
Solution

Re: OODB V.S Relational DB (e.g. Oracle)

Yogeeraj_1
Honored Contributor

Re: OODB V.S Relational DB (e.g. Oracle)

hi chris,

First off, in Oracle you would be considering pure relational versus Object RELATIONAL, not OO. We have object relational extensions to the relational database. We do not have an object oriented database.

The answer to this comes down to the data you are working with. Let's say you are building a banking application. You are building the application for the teller to service a person when they walk in the door. The Object perfect for that application is a "person" object identified by name or account number. That person object has all of the attributes of a person in a bank, a name, an address, a list of accounts with all of the account attributes, a list of recent transactions, and so on. A big glob of data that represents all of the information about a person. That is the perfect view for the teller. HOWEVER, at the end of the day, there is someone else who has a totally different view of the data -- they need to count how many transactions happened that day. How much money is in the bank. They have a transaction oriented, not person oriented, perspective of the data. In this case, a RELATIONAL model with
possibly application specific Object relational views built on top of it is perfect. You need an account table, that is joined to a transaction table and a person table. In that fashion, the guy who needs to count the transactions is satisfied and so is the guy who needs the person oriented view.

That is the power of the relational model, it is able to easily give many views of the same data. Think of it this way with the scott/tiger EMP, DEPT tables. It might seem to make sense to create an EMP object type, a nested table of EMP, a DEPT object with an attribute of EMP nested table and then a table of DEPT types. Now the whole scott/tiger emp/dept example fits into 1 table with 4 rows. Sounds great. The problem is people will ask questions like:

o how many emps do I have?
o KING is standing here at the front door -- is he an employee or not?
o how much salary did I pay accountants last year?

and so on. None of these questions are easilly answered with a DEPT oriented view of the data.

Just some food for thought. I've not really used the Object relational concepts as a STORAGE mechanism, I have used them in my programming with PLSQL lots. I tend to stick with real tables and use the objects in my code frequently.

hope this helps!
Best Regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Chris Fung
Frequent Advisor

Re: OODB V.S Relational DB (e.g. Oracle)

Thanks for the comments !!

To me the OODB implementation right now is more suitable for web applications which are built on Java. As a result, the object status can be easily written to the OODB with just only a litte investment in the design of OODB, because the objects/classes are already defined in the programs themselves.

However, as Yojeeraj said this kind of OODB may not be suitable for the decision support queries.

Just wondering the future trend in the DB world......will OODB be dominated ?

Cheers,

Chris,
Steven E. Protter
Exalted Contributor

Re: OODB V.S Relational DB (e.g. Oracle)

Though oracle is a "pure" relational database, there are "Object Oriented" development tools that work with the data.

You can have BOTH!

I think that the relational model is very powerful. I mean you've got a cusmter with one master record and customer number, He's got six invoices with a total of thirty items purchased.

It all gets tied together by the customer number. Triggers get activated as the invoice is entered.

Quite cool.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Indira Aramandla
Honored Contributor

Re: OODB V.S Relational DB (e.g. Oracle)

Here are few links for some info.

1. Oracle8 and Object Relational Database: An Overview: An Oracle Technical White Paper
link -http://otn.oracle.com/products/oracle8/info/objwp3/xoo3twp.htm

2.Object Relational Technology: Object-Relational Technology... (published 09/17/2002)
link - http://otn.oracle.com/products/oracle9i/htdocs/ort_twp.html

3. Oracle8 Object-Relational Database: A Glossary of Terms: An Oracle Technical White Paper
link- http://otn.oracle.com/products/oracle8/htdocs/xo8twpg3.htm
Never give up, Keep Trying
Yogeeraj_1
Honored Contributor

Re: OODB V.S Relational DB (e.g. Oracle)

hi,

A very interesting discussion on this URL:
http://groups.google.com/groups?q=OODB&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=1561%40dinl.mmc.UUCP&rnum=2

please check.

Regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)