Re: Decline of Science: Computer Science and Databases

Lauri Pietarinen wrote:
> > SELECT FROM Consultant, Coach WHERE .salary > 200000;
>
> Is'nt it rather a union than a join?

Yes, sorry.

> As a general remark I would say that the relational approach
> requires more planning in the sense that you have to design and
> create a database schema (=data modelling). However,
> the reward is that
> - extremely complex queries can be formulated
> - arbitrary integrity constraints can be enforced
> ( referential integrity being only the simplest case)
> - queries can be optimised by an optimizer

Why would any of the above not be possible with an object oriented approach?

> How does this fit in with OO-programming?

It does, syntax just looks different.

> Well,
> the idea actually is to get rid of programming as
> much as it is possible ;-)

I think this approach is wrong.

We want development at all levels:
- More precise code at low level.
- More powerful syntax at high level.

One of the best languages we have developed is our human language. It sure is not pure relational math.

I would rather say it is object oriented:

You build up a temporary context of small "objects" and refer to them in subsequent "methods". The "object" context is temporary and get's overridden by subsequent "objects" that overload meanings.

Hey, this is just like dynamic delegation!

Kind regards,
Carl

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