Re: Is a Query langauge really necessary in an OODB?

In article <8b34be$qj6$1_at_nnrp1.deja.com>, Brian Price <brianleeprice_at_hotmail.com> wrote:
> Is a query language really necessary in an OODB? Assume a small
> business database. I know what the OODB manifesto says, but practical
> experience tells me otherwise.
> Even with RDBMS, a query language seems to be primarily of use to the
> developer of the database. My customers never use SQL, or even the ad-
> hoc query generator, in fact they seldom make use of the custom query
> wizards I've written.
> In OODBMS, the situation would seem even more biased against query
> languages. Why do I, as a developer, need an interpreted query
> language, when I can simply iterate through a collection? If I need
> scripting capability, I can always implement part of the solution in
> Java. What would a query language be except an unneccessary
> intermediary?
> --
> Brian L. Price
> Have compiler will travel.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
One of the nicer benefits of a query language is that 3rd party tools can be used.
For example, report writers like Crystal Reports. If each OO application has it's own collection and accessor protocols, then it is probably harder to use such a generic tool. Just sompin' to think about, -tmind-

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Mon Mar 20 2000 - 00:00:00 CET