[Tutor] What's the catch with ZopeDB?
knacktus at googlemail.com
Fri Jun 11 21:42:35 CEST 2010
I'm planning to create small application which manages product data e.g.
parts of cars. There are quite some relations, e.g.
- a car consists of certain assemblies,
- an assembly consists of certatin parts,
- a part has serveral documents which describe the part, e.g. a CAD
document or material data.
So, one could think of storing the data in a relational database. But
now I start to think ... ;-):
- I would just need some predefined queries which would be performed by
Python code, of course. Maybe using an ORM.
- Therefore, I don't think I need all the power and flexibility of SQL.
- I will work with Python objects. Why should I translate to an
relational schema "just" for persistence?
- Performancewise, caching is probably much more sensitive than pure
database performance. (That my guess...)
To me, ZopeDB (a object database for Python) looks like an awesomely
easy solution. I could save some brain power for the innovative part or
drink more beer watching the soccer world cup. At the same moment, I
wonder why anyone in the python world would go through the hassle of
using relational databases unless forced.
So, has anyone experience with ZopeDB? Are there some drawbacks I should
be aware of before getting a book and dive in? (It sounds too good ;-))
More information about the Tutor