Re: The IDS, the EDS and the DBMS

"Laconic2" <laconic2_at_comcast.net> wrote in message news:<rsqdncziiclazKrcRVn-tA_at_comcast.com>...

> The IDS is the classic DBMS of the 1970s or 1980s to me. It costs more to
> get data into the database than to get data into a file

I don't want that DBMS! :)

>, but you get more
> value out of the data by using it to support more processes.

And what about declarative data management?

> What do I mean by an EDS? Roughly, it's this: a database is built to
> provide persistence to some data in an object oriented environment.

Do you mean: to save a main memory network structure into a disk?

> That is, there is a certain class of objects that "knows" how to interpret
> all the data in the database, knows how to operate meaningfully on it, and
> knows how and when to write data to the database.

A procedure that stores a network of values into a disk.

> That is, the OO system uses inheritance and messaging to enable
> integration.

It uses the network approach and procedural data management.

> It seems to me that many discussions in this forum have degenerated into
> tirades because some of us have the IDS so deep under our skins that the EDS
> strikes us as chaos, and the result of ignorance.

The "EDS" is the prehistory of the computerized data management.

> Others have the EDS so
> deep under our skins that the mere concept of the IDS seems at best quaint,
> and at worst counterproductive.

In other words: they don't have a good grasp on the fundamentals of modern data management.

> But my purpose in this discussion is to move the IDS and the EDS from the
> realm of unconscious reaction to the realm of conscious thought. That way,
> the discussion between "IDS types" and "EDS types" can be rational and
> analytic, instead of visceral and parochial.
>
> What do you think?

The topic was closed in the mid 70's. There is nothing new to say.

Regards Received on Fri Sep 03 2004 - 14:19:45 CEST