Re: Mixing OO and DB
Date: Fri, 08 Feb 2008 16:44:53 +0000
Message-ID: <foi0v0$f6g$1_at_aioe.org>
> On Fri, 08 Feb 2008 13:48:50 GMT, David Cressey wrote:
>>I think it might be interesting to explore the whole concept backwards: >>start with the idea that a table is just a specific class of object
>Then come up with two things: how to store persistent objects and
>retrieve them when
>necessary without regard for any data model; and how to get tables and
>application objects to collaborate on common objectives.
If the implementation is a computation process, there is also no guarantee that each instance in Somewhere actually use the *same* implementation.
So all the optimisation etc that is achievable when you constrain x/y/z to be raw data values only, is lost when you can no longer presume such constraints.
It is because of this that I believe that the only paradigm that is capable of providing the true engine for a relational info base that caters for both OO and current RDBMS, is Functional programming (data values and computation entities - functions - are treated the same, techniques such as lazy evaluation, "copy on write" behaviour etc) .
Regards,
Steven Perryman
Received on Fri Feb 08 2008 - 17:44:53 CET