[ZODB-Dev] How do you handle changes to BTree key values?

[Patrick K. O'Brien]

I went back and reread the archived messages where you talked about
developing a StandaloneCatalog for just this thing. I would love to see more
support for the goals that you outlined at
http://lists.zope.org/pipermail/zodb-dev/2001-May/000837.html. Where does
this stand? Is anyone helping to make it a reality?

---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."

-----Original Message-----
From: zodb-dev-admin@zope.org [mailto:zodb-dev-admin@zope.org]On Behalf Of
Christian Robottom Reis
Sent: Wednesday, October 10, 2001 5:36 PM
To: Michel Pelletier
Cc: pobrien@orbtech.com; ZODB
Subject: Re: [ZODB-Dev] How do you handle changes to BTree key values?

On Tue, 9 Oct 2001, Michel Pelletier wrote:

> Probably. ;) ZODB really just provides you with an "object universe"
> that is persistent over time.  This persistence of your data is realy
> the only thing it has in common with a relational database.  The data

Just to reiterate here, this is something I've had to wrap my brain around
with the ZODB. It is a persistence mechanism, but by default it includes
no retreival mechanism or indexing.

This means that _you_ are responsible for telling the ZODB how to store
information based on how you plan on retrieving it. You need a specific
storage and retrieval plan, though you can accomodate for changes later by
adding other indexes.

> In a relational database, you need to use keys, tables, rows etc
> because the data model constrains you to that.  For certain problem

The relational model also provides you with an interesting mechanism for
retrieving your persisted information, where it can correlate with similar
data in other relations and columns. This is a very important aspect of an
RDBMS that hasn't been hashed out enough here: when you abandon it, you
are not only abandoning persistence but retrieval and indexing (optimized
retrieval, IOW).

When you choose to use ZODB, you agree to cook your own. If this is
acceptable, as it is to me, the unbelievably simple to use persistence
mechanism can really shine.

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL