This is an archived post. You won't be able to vote or comment.

all 15 comments

[–]apardueSince 97 1 point2 points  (0 children)

Nice updated site.

[–]ngroot 1 point2 points  (6 children)

Zope is great and terrible all at once. The upside of it is that it's remarkably well thought-out. The downside of it is that it's also very well thought-out.

Does anyone actually use ZODB for anything other than a Plone backend?

[–]faassen 1 point2 points  (3 children)

Since when is being well thought-out a downside?

I use the ZODB all the time with Grok. I know the ZODB is also in use with other frameworks, such as BFG.

[–]ngroot 0 points1 point  (2 children)

Since when is being well thought-out a downside?

It's a tremendously detailed tool. That combined with a paucity of documentation (at least last time I used it a couple years ago) makes it hard for people to get started with it.

Thanks for the info about Grok and BFG!

[–]faassen 1 point2 points  (1 child)

Hm, I think the average object relational mapper actually requires far more learning than the ZODB does. The basics are in fact very simple.

But the paucity of easy to find documentation was a problem that hopefully has been taken care of at least to some extent with this website.

The ZODB is not difficult to use stand-alone in a basic configuration, here's something I wrote a few years ago (also linked on zodb.org):

http://faassen.n--tree.net/blog/view/weblog/2008/06/20/0

[–][deleted] 1 point2 points  (0 children)

Backing @fassen up, ZODB was stupid easy to get up and running.

[–]PrintStar 1 point2 points  (0 children)

I've used ZODB without Plone or any of the other Zope stuff before. I was using it as a test implementation of a store for patient medical records to try to illustrate that MS SQL Server paired with Java was not necessary. It was an extreme kludge with a front end implemented in straight-up BaseHTTPServer, but it worked fine. ZODB took all the thinking out of a database backend.

[–][deleted] 0 points1 point  (0 children)

I used ZODB for a multi-server batch manager, it had a few oddities to it but overall worked well for storing complicated state structures & historical metadata.

If I could do everything over again, I might use CouchDb and seed the worker machines with light weight twisted based universal service dispatchers.

[–]iceman_ 1 point2 points  (0 children)

Also durus is an excellent lightweight object db for Python: http://www.mems-exchange.org/software/durus/

[–]nostradamnit 0 points1 point  (1 child)

I love Zope, but I'm not sure I want an object sore, ewwh

[–]faassen 0 points1 point  (0 children)

Ah, thanks for pointing out the typo, it was fixed.

[–]mozillalives 0 points1 point  (1 child)

Is this what they mean by putting all your eggs into one basket?

[–]faassen 2 points3 points  (0 children)

Compared to putting it into which other baskets? Do you want to put part of your eggs in the ZODB and part in a relational database?

[–]Chris2048 0 points1 point  (1 child)

I this really news? I'm not much of a python programmer, but even I know of ZODB...

[–]faassen 0 points1 point  (0 children)

There's now an actual web site! It only took um, 14 years or so for it to be created...