[Zope-dev] Re: Alternative Storages: (was RelationalStorage (was LocalFS))

[Jason Spisak]

Jimmie Houchin:

> At 11:16 PM +0000 5/3/00, Jason Spisak wrote:
> [snip]
> >> Multiple file storage for the ZODB has been proposed as a solution and
> >> there are 2 proposals currently on the ZODB ZWiki. I will add another.
> >>
> >> Class/Object based db files.
> >
> >Maybe we are talking about the same thing here.  Are you talking a db (like
> >Berkeley) implementation of the MultipleFileStorage?
> 
> Some type of MultipleFileStorage. A primary difference in our ideas from my
> understanding is in my idea it is a single file per class instead of a file
> per object. Which is what I described below.
> 
> 

What is the primary reasoning behind the per class?  Is that how the ZODB
works now? I think it's transaction based.  I think I understand now.  It's
like a row in an RDBMS.  Yes, we are talking about two different animals. 
I think the important thing is the transparency of as Phillip said
"persistance providers".  A place to get you persistance, whether stored by
class/object/transaction, they should all give Zope what it needs...an
object with a current transaction/version state.

> >> Each class gets it's own db file. This could be similar to the current
> >> ZODB file except specific to a class. As objects are created they are
> >> appended to the db file for their class. This could be somewhat
> >> analogous to tables in an RDBMS.
> [snip]
> 
> 
> Thanks.
> 
> Jimmie Houchin

All my best

Jason Spisak
CIO
HireTechs.com
6151 West Century Boulevard
Suite 900
Los Angeles, CA 90045
P. 310.665.3444
F. 310.665.3544

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.