Possible bridges between OO programming proponents and relational model

such thing really exists (and in fact is not necessary). In a word, In

OO approach (for whatever it may rely on), one of the main limitation of relational model would be not to allow its elementary components to emulate elementary predefined processes (transformations for instance).

I have the impression, there is a concept, unbearable to some programmers that data management systems can not be anything else than a mechanized set of tool that could help structuring data for human interpretation. On that standpoint, relational model components reflect an approximation of *meaning* concept as being a contextualized

and specific combination of constraints, business rules to make predefined inferences about that data for preparing interpretation. Processes are defined only according to specifically defined inferences. On the other side, OO approach seems to advocate that some

level of elementary process autonomy will end up creating *some* form of intelligence thanks to some cumulative effect. On such perspective, I start suspecting all debate stating behavior lacking in the relational model is an empty unfounded attempt of some IT professional to project their scifi fantasies about what system could do and what they can actually do in a realistic manner.

On the other side, some OO advocates state that OO approach brings some

features that would seem to better implementations of subtype and supertypes features through inheritance as well as a better in memory physical handling of non primitive types than what we are accustomed to

with traditional SQL implementations.

I am curious about your opinion about this matter as this is a new board for me. (Sorry if you have noticed some english errors as it is not my native language) so bear with me please. Received on Tue May 30 2006 - 21:31:17 CEST