If it's embedded, is there any reason why it should be SQL? A solid
alternative could me MetaKit, which has Python bindings:
http://www.equi4.com/metakit/python.html
"""
Buzzwords - Metakit is an embeddable database which runs on Unix,
Windows, Macintosh, and other platforms. It lets you build ap
My opinion, as posted there, was pretty immediate and only going off of
surface values. I just saw in Django what I had seen too much of in my
own code. I've written similar things in Zope and Formulator that did
all sorts of fancy automatic 'admin screen' generation, DBMS CRUD
statements. I even a
Zope 3, far and away. There's great documentation, quite a few load
handling options (different types of caching and ZEO to distribute ZODB
caches to multiple machines). Zope 3 aggressively favors small
cooperating objects (Zope 2 was inheritance heavy, making
customization, extension, etc, a big c
The ZODB (Zope's object database, which can be downloaded and installed
separately from Zope) and Durus (part of the Quixote family, I believe)
are both high quality persistent Python object stores that are used
heavily for web sites.
I've never used the ZODB outside of Zope, and haven't used Duru