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

Re: OODB query interface



>
> >   Therefore, I suggest that the prime query language is the language of the
> > API in an object oriented fashion, and that different graphical and natural
> > language interfaces are implemented on top of that.
>
> I perfectly agree here.
>
> To be real object oriented the query interface has to provide a language
> dependent API. This has to implement the query model (which we will have to
> specify) into the underlying programming language. Front ends for that API may
> be developed on top of that.
>
> >
> >   But let's skip the skin and dive into the gore: what types of operation does it need to support?
> >
> >   I have come up with three kinds, two of which operates on sets (or bags) of objects, and one that operates on objects:
> >
> >   1) Normal set algebra on objects (joins etc)
> >
> >   2) Filtering, that is selecting subsets of objects that meet certain criteria (like WHERE clauses)
>
> Exactly. We need a way to define sets (subsets) of objects (filtering) and set
> algebra functions to be used with these sets.
>
> >   3) Following references.
> Why? Can you explain more?

I think he means:

Class A {
    private B b_ref;
}

Class B {
    private int i;
}


select * from A where A.b_ref.i = 1


Maybe?

Also, can searches be done in ozone on private variables?

Jake ...