[DISCUSSION] Object Relational Mapping (ORM) - faulting/collections

[Ruslan Zasukhin]

On 11/10/07 10:51 AM, "Philip Mötteli" <philip.moetteli at econophone.ch>
wrote:

Hi Philip,

>> I was told on Cocoa list, that its true that if table T5 has million
>> records, then system prepare million small RAM objects for future
>> faulting.
>> 
>> IMO this is huge overhead.
>> IMO this is limited way by hardware.
>> 
>> So is this true that all million objects are prepared?
> 
> Yes.

> But, objects, that collect other objects are collection objects.

Agree.

> OO  
> is about reusing code. So a programmer shouldn't re-implement
> collection objects. He should reuse the ones, that are already there.

100% agree.

> Which means, that the persistence library can also replace them or
> part of them, so that they use an optimized memory management.

As I have always told -- my believe is:

    db engine must know as many as possible
    about 
        Tables, Fields, Links, Properties,
        types of links,
        methods, inheritance, polymorphism,
        collections (sets, lists, arrays, ...)


When COLLECTIONS will be PART of DATABASE STRUCTURE (!!!)
    then OR Frameworks will become more and more simple.
   

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]