Storing lots of (unnamed?) objects with ozone

Hi there.

I'm currently working on a quite big web portal project (design
stage/proof of concepts/evaluation currently) and - since I'm really
annoyed by SQL in code and interested in a completely oo-oriented design
I found this project. I read the documentation and samples and played a
little with it, but I still have some questions that arise:

1)
I need to store lots (thousands/more) of persistant objects. Since I'm
not (yet) used to this design paradigm: How can I efficently store (and
more important: retrieve) such objects? My first thought was to
implement a persistant ListObject for any type of object I need to store
and to use my own stubs to make sure that I
a) don't have all objects in memory as soon as I want a single one
b) don't need to name all objects (linked lists perhaps?)
Has anyone done this? This is supposed to be a web application. Is the
performance (given that I design it the right way (TM)) sufficient with
really lots of objects?

2)
I really have problems (headache..) to think about both ozone and
different views on my objects/data.. I try to avoid the word selection
here, but - that's what it ends up to be.. Do you know any howtos/guides
to handle something like "Get me all of my users that live in Canada and
don't speak french"?

I'd be glad to get a little help, even if it reads "Go back to google
again" or "Sorry, I think you want to stick to relational databases with
your requirements/current knowledge about oodbms".

Thanks in advance,
Ben



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click