[Pythoncard-users] Why ZODB?

[Patrick K. O'B. <po...@or...>]

Here is a good answer to the question of why we might want ZODB for
PythonCard, from the article by Michel Pelletier at
http://www.zope.org/Documentation/Articles/ZODB1:

<quote>

ZODB is a database for Python objects that comes with Zope. If you've ever
worked with a relational database, like PostgreSQL, MySQL, or Oracle, than
you should be familiar with the role of a database. It's a long term or
short term storage for your application data.

For many tasks, relational databases are clearly a good solution, but
sometimes relational databases don't fit well with your object model. If you
have lots of different kinds of interconnected objects with complex
relationships, and changing schemas then ZODB might be worth giving a try.

A major feature of ZODB is transparency. You do not need to write any code
to explicitly read or write your objects to or from a database. You just put
your persistent objects into a container that works just like a Python
dictionary. Everything inside this dictionary is saved in the database. This
dictionary is said to be the "root" of the database. It's like a magic bag;
any Python object that you put inside it becomes persistent.

</quote>

---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."