This is the mailing list for discussions related to the ZODB.

ZODB makes Python applications persistent. Just subclass `Persistent`, and your objects and application become persistent. ZODB is in heavy use in the Pyramid community, and since around 2003 in even heavier use in the Plone Community. Multiple people report ZODB to be rock solid. No Zope required.

ZODB has significant advantages over other persistence technologies. In relational databases it is hard and slow to store a tree. JSON databases do store trees but not graphs. MongoDB has problems with fine-grained transaction management across document boundaries. PostgreSQL has excellent transaction management, but does not support arrays of heterogeneous objects. And of course once you are in a pure dynamic Python environment, there are all kinds of things that you can do that you could not even imagine doing with a traditional database.

ZODB is useful for building JSON servers. There are a large number of Python libraries which support JSON. Javascript does not have a `__getattr__` method, and would block on object fetching, so don't wait for something like ZODB to appear in the Javascript world anytime soon.

To summarize, ZODB makes it really easy to build and distribute persistent Python applications.

zodb

Description

Language

Privacy