Re: Unknown SQL

Bob Badour wrote:
> >> >arrays, n-dimensional arrays, classes without public constructors,
 inner
> >> >classes, all JDK Collection classes, simple types, interfaces ...
> >>
> >> So many concepts, so much complexity. Beyond making things more
 difficult
> >> for users, what good is it for?
> >
> >All of these concepts are part of the Java programming language.
>
> All of these concepts are part of your data model. The fact that you
> borrowed your data model from Java in no way makes your data model any
> simpler.

No sorry, we do not borrow the data model. We simply try to support the class model that is present.

> Just try to teach an end-user to write Java code in their
> interactive query tool! LOL

We are working on a graphical user interface to query stored objects without the need for a query language.

> >If you see
> >a concept that could be replaced by a better one, please send an RFE to
> Sun.
>
> Sure. Replace Array with Relation. Replace Bag with Relation. Replace Set
> with Relation. Replace Collection with Relation. Class and Domain are
> equivalent so it matters little which name one uses. Replace Iterators
 with
> set-level operators. Um, I could go on for quite some time, but I am
 getting
> thirsty.

As I just posted, you can't write any programs in "relational". Or could you a write a newsreader in "relational"? Objects are there and used, that's a fact. The Java JDK is there and the classes are being used, that's a fact. We try to store them as they come.

All the relational equivalents that you posted are

- unnecessary extra concepts to learn
- unnecessary extra code
- bad for performance

> >Every concept, additional or renamed:
> >- introduces standardization problems between vendors
>
> It introduces much more than standardization problems. Aho et al. mention
> that one of the most effective optimization techniques is algorithmic
> replacement. How many object oriented languages or OODBMSs do you know
> capable of algorithmic replacement? Every SQL product on the market
 performs
> this extremely potent optimization technique. Even small-footprint
 products
> like Lee's!

I am sorry but I don't understand what you mean with "algorithmic replacement".
Could you please post further information or an example? Thanks.

Kind regards,
Carl

---
Carl Rosenberger
db4o - database for objects - http://www.db4o.com