Collection Object

Ruslan Zasukhin sunshine at public.kherson.ua
Wed Aug 2 18:49:21 CDT 2006


On 8/1/06 6:37 PM, "Philip Mötteli" <philip.moetteli at econophone.ch> wrote:

>>> I have another proposition how we could approach the problem (instead
>>> of looking how Postgres possibly does it): Lets assume the following
>>> M:M intermediate table:
>>> 
>>> MMIntermediate
>>> {
>>>    collectionRecord as ObjectsPtr,
>>>    nextRecord as RecID,
>>>    memberRecord as ObjectsPtr
>>> }
>> 
>>>       ..........    PICTURE ...............
>> 
>> 
>>> (For the moment just ignore the 'nextRecord', which is there only to
>>> create an ordered collection).
>> 
>> okay
>> 
>>> So this MMIntermediate table would play the M:M table, joining the
>>> collection table (e. g. NSSet) to the destination table of the member
>>> object (here displayed by taking the root of all Foundation objects:
>>> NSObject).
>> 
>>> This would replace the array kind of field, proposed by
>>> Postgres and Ruslan.
>> 
>>> How would searching work in this case? I mean, here too, I can search
>>> for a field of the member record, that possibly doesn't exist?
>> 
>> Philip! :-)
>> 
>> And here you have describe nothing else as solution based on
>> inheritance
>> which I also have show 1-2 days ago. Please find my letter.
>> 
>> * We have some ROOT table  == NSObject
>> 
>> * Tables T1 T2 T3 are inherited from this table.
> 
> What do they inherit?

Class T1 : public NSObject
{
}

What it inherit ?

    * Some RTTI ?
    * Ability to be NSObject

Right?

The same for tables:

    CREATE TABLE T1 inherit NSObject



-- 
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]




More information about the Valentina mailing list