| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Guidelines for using Oracle 9i Object Relational Features
Hi,
Maybe that's true for Oracle OO song-and-dance but ...
I've just started investing heavily into Oracle 9.2's XML support and XML Schema technology. So far, nothings working (surprise!) but I think I'm getting closer.
Anyways, the XML support does make use of Object-Relational table structures. I tried just using OEM to read XML definition file -- and it automatically creates this OR table -- actually just a single XMLType table but a bunch of Object Types too.
Relational technology has been around forever (ok, a really long time) and Oracle (and others) have done a pretty darn good job of making it work quite well. Now along comes this wrinkle of XML to help "enable" messaging more descriptive information to data repositories. No one says you "have to" store XML in the DB and, in fact, the docs suggest 4 ways of handling it including using XSL to transform the data into relational tables (and back).
Seems like a good idea so far.
"DA Morgan" <damorgan_at_exesolutions.com> wrote in message
news:3E1C9327.79D21E_at_exesolutions.com...
> "S.T.Arun" wrote:
>
> > Hi,
> >
> > I would like to know if there is anyone who has used Oracle's Object
> > relational Features in a live project. If so, I would like to have
> > some guidelines on do's and don'ts, the problem faced, solutions to
> > them (if they exist!!). Most important of all the performance
> > comparision between using ORDBMS and RDBMS.
> >
> > We are to propose the usage of Oracle 9i Database with OO
> > implementation using Pro*C/C++ and Java. Any help in this regard
> > would be great.
> >
> > Thanks in advance.
> >
> > Regards
> > Arun
>
> I would stay as far away from OO in the database as you can.
>
> OO databases, as can be clearly seen by their less-than-impressive
> marketshare were all marketing hyperbole except in a few limited
> applications. The syntax more difficult. The performance nothing to
> note. It is one thing to use OO techniques in your front end but they
> don't really belong in the back unless there is a compelling reason.
>
> And in the case of writing against a database you should not be putting
> any SQL into the front-end unless the object of your development is to
> make something difficult to tune, difficult to upgrade, and a monster to
> debug. Don't believe me? Ask people here how much they love Siebel and
> PeopleSoft.
>
> Daniel Morgan
>
Received on Fri Jan 24 2003 - 08:08:10 CST
 |
 |