[Zope-dev] Proposed solution for ZODB woes

[Dyon Balding]

On Fri, Feb 18, 2000 at 08:37:38PM -0500, Kevin Dangoor wrote:
> Though I admit that I'm not familiar with the inner workings of this part of
> Zope, I have a feeling that what you're suggesting is a lot of work. There
> is an existing alternative right now in the form of SQL databases. Just
> store any of your frequently changing things (hit counters and the like) in
> there.

the hassle of maintaining and administrating an SQL database in addition to
Zope doesn't seem to me to be worth it.  in a small environment that is fine,
but when it comes to hosting it would be much  nicer if everything was
centralized (and in Zope :).

> 1) Longer term, Jim has talked about being able to use multiple storages
> simultaneously. This would allow you to set up one storage for your
> frequently changing stuff and one for your less frequently changing things.

yep. multiple storages are a solution to a number of problems at the moment.
what is the current status of multiple storages?

> 2) Or, implement a new storage (maybe an SQL storage). There's already
> Berkeley Storage, which doesn't have the growth issue of FileSystem, but
> also doesn't support versions and undo. If you make a storage that attaches
> to Postgres, you can probably get everything.
> 
> Gotta love a system as extensible as Zope :)
> 

-d

-- 
                            Dyon Balding, email: dyon@adroitnet.com.au
                           work: +613 98888522, mobile: +61 0414992604
                                             Adroit Internet Solutions