A new version of ZODB has been released, 3.10.5. You can find more information at python package index, http://pypi.python.org/pypi/ZODB3/3.10.5 also while lurking on the zodb-dev mailing list; it appears that ZODB 3.11 has been getting some work. It is possible Q1 2012 a new release emerges.
Still looking for people who are interested in contributing to the ZODB documentation.
Tuesday, November 29, 2011
Tuesday, June 14, 2011
API documentation uploaded
Carlos is continuing work, with some help from the community, on the ZODB book. Currently you can see daily updates at http://zodb.readthedocs.org. The new API section, http://zodb.readthedocs.org/en/latest/api.html lists the entire zodb/transactions API on one page -- thanks Dag Odenhall. Now if we could get richer descriptions on the method's. We are looking for volunteers. Some suggested topics:
- Conflict resolution
- BTree usage
- ZEO aka "Client Storage"
- Demostorage usage and real world examples
- PickleCache
Saturday, April 2, 2011
Chapter 4, Transactions
ZODB.org is having problems with git integration. We are temporarily moving to http://readthedocs.org to have documents built on commit. Please give us feedback!
This is the first comprehensive documentation on the transaction package.
ACID (atomicity, consistency, isolation, durability) is a very convienent feature of ZODB. Along with transactions it makes programming ZODB an enjoyable experience for the Python programmer. All persistent ZODB operations are controlled by commit/abort using the transaction package. Carlos describes integration points including datamanagers, synchronizers, and commithooks -- all integration points to wire custom code into participating with transactions. One such integration is zope.sqlalchemy which provides coordination of transactions between ZODB and SQLAlchemy data sources.
This chapter is longer than all three of the preceding chapters. It is the first comprehensive documentation on the transaction package. And it's the first chapter to use our favorite web framework Pyramid to demonstrate usage in a web context. Remember the transaction package does not depend on the ZODB. Spread the word.
This is the first comprehensive documentation on the transaction package.
ACID (atomicity, consistency, isolation, durability) is a very convienent feature of ZODB. Along with transactions it makes programming ZODB an enjoyable experience for the Python programmer. All persistent ZODB operations are controlled by commit/abort using the transaction package. Carlos describes integration points including datamanagers, synchronizers, and commithooks -- all integration points to wire custom code into participating with transactions. One such integration is zope.sqlalchemy which provides coordination of transactions between ZODB and SQLAlchemy data sources.
This chapter is longer than all three of the preceding chapters. It is the first comprehensive documentation on the transaction package. And it's the first chapter to use our favorite web framework Pyramid to demonstrate usage in a web context. Remember the transaction package does not depend on the ZODB. Spread the word.
Subscribe to:
Posts (Atom)