[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: JDO and OODBMS


Castor's JDO was implemented before the spec came out. The current JDO spec
is very OODBMS centrice and does not apply well to relational database
models which Castor supports, along with other persistence options (xml flat
file, LADP, OODBMS...). Either the JDO need to be changed or Castor will be
forced to have it's own variant of JDO.

Interesting to see what happens.

-david


> -----Original Message-----
> From: Falko Braeutigam [mailto:falko@softwarebuero.de]
> Sent: Friday, June 09, 2000 10:29 AM
> To: David Duddleston; ozone-users@ozone-db.org
> Subject: RE: JDO and OODBMS
>
>
> On Fri, 09 Jun 2000, David Duddleston wrote:
> > JDO would be nice. Lets see how the spec pans out once there is
> a reference
> > implementation.
> Castor claims to be JDO. But I was told that there is not to much to see
> actually. Anybody familiar with Castor's JDO?
>
>
> Falko
>
> >
> > -david
> >
> > > -----Original Message-----
> > > From: Falko Braeutigam [mailto:falko@softwarebuero.de]
> > > Sent: Thursday, June 08, 2000 11:01 AM
> > > To: ozone-users@ozone-db.org
> > > Subject: Re: JDO and OODBMS
> > >
> > >
> > > Charles, thanks for the info.
> > >
> > > On Thu, 08 Jun 2000, Charles Benett wrote:
> > > > Ozonies,
> > > > FYI. There's an article on Java Data Objects and both relational and
> > > > object-oriented databases at www.javareport.com. Looks like some
> > > > commercial OODBMS vendors are involved. Any ideas how ozone
> will react/
> > > > fit in?
> > > I'm not yet sure. What do the others think?
> > >
> > > We have to check the actual API of JDO to find out
> > > 0. If anybody needs ozone/JDO?
> > > 1. If we are able to support JDO with ozone.
> > > 2. If yes, do we loose some of special benefits of the ozone
> architecture.
> > > 3. If we are able to provide a fast JDO implementation on top
> of ozone.
> > >
> > > To answer these questions we have to discuss many points. One of
> > > them is that
> > > JDO supports a query language and IMO every query lang othen than the
> > > underlaying programming lang (Java in our case) permits us to
> reach the
> > > goal of closing the impedance mismatch between app and database logic.
> > >
> > > Other ideas?
> > >
> > >
> > > Falko
> > > --
> > > ______________________________________________________________________
> > > Falko Braeutigam                         mailto:falko@softwarebuero.de
> > > softwarebuero m&b (SMB)                    http://www.softwarebuero.de
> > >
> --
> ______________________________________________________________________
> Falko Braeutigam                         mailto:falko@softwarebuero.de
> softwarebuero m&b (SMB)                    http://www.softwarebuero.de
>