durusmail: durus-users: OODB basics
OODB basics
2005-10-08
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-11
2005-10-12
Re: OODB basics
2005-10-11
OODB vs SQL
2005-10-09
2005-10-09
2005-10-09
Re: OODB vs SQL
2005-10-10
Re: OODB vs SQL
2005-10-10
OT: Durus
2005-10-13
2005-10-13
2005-10-13
2005-10-09
2005-10-09
2005-10-09
2005-10-10
2005-10-11
2005-10-11
2005-10-11
2005-10-11
Re: OODB vs SQL
2005-10-11
2005-10-11
2005-10-11
2005-10-12
2005-10-12
2005-10-12
Demo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
Re: OODB vs SQL
2005-10-11
Durus basics
2005-10-09
2005-10-09
2005-10-10
2005-10-10
2005-10-10
2005-10-13
2005-10-13
2005-10-13
2005-10-13
Re: OODB basics
2005-10-13
OODB basics
Oleg Broytmann
2005-10-09
Hello! Thank you for replying!

On Sun, Oct 09, 2005 at 10:02:05AM -0400, David Binger wrote:
> Are you talking about iterating over the keys of an index, and loading
> some subset of the values based on information that is encoded in
> the keys?

   Yes, exactly. I'd like to write a program that will do all kind of
searches through a huge list of objects, and I need to make the program
speed- and memory-efficient. Iterating over indices seems like a good (if
not the only) approach.

> References are really the dominant structural feature.

   What is a "reference"? You don't mean deep object hierarchies (a.b.c.d),
do you?

Oleg.
--
     Oleg Broytmann            http://phd.pp.ru/            phd@phd.pp.ru
           Programmers don't die, they just GOSUB without RETURN.
reply