Re: parent/child relationship in the same table.

From: James <jraustin1_at_hotmail.com>
Date: 18 Nov 2001 07:49:12 -0800
Message-ID: <a6e74506.0111180749.3c175961_at_posting.google.com>

> > Object folks thinking is frozen in terms of nested loops
> > that user has to write.
> If you pulled a marble out of a bag and it was black, you would say
> that the remaining marbles in the bag are black. What are your chances
> of being correct?
My apologies, I am guilty of this also :)

An error on my part, the below claims are for resolving a child's parent and not a parent's children which was the original topic.

1. oodb is faster at resolving parent/child relationships?
2. resolution time in rdb increases with # of records?
3. resolution time in oodb is constant regardless of # of "recs"?

But I still believe, in general, an oodb will resolve relationships faster.

> ...resolves parent/child relationships
> at a rate of 100 mil/sec on a 800Mhz PC?
Please ignore this specs as it is a number under ideal test condition and not representative of real world situations.

Would you like to benchmark a rdb, with or without "pipelining", with XDb in a specific case similar to the original problem? Received on Sun Nov 18 2001 - 16:49:12 CET