Forgive an important but nieve( I think) concern. If I start to use Zope as a database I'm concerned about database corruption and transferability. When a table becomes corrupt in Access it is usually easily fixed or replaced from backup as a last resort. I think PostgreSQL uses seperate files for it's tables so the can be replace if needed. What happens if the Zope database gets corrupt? It is a monolithic file. Also, what about exporting data for use in a different database or program? Can I read the zope database with ODBC? If I ever needed to convert to another database what about exporting the data? These are questions I'm going to have to answer in justifying introducing Zope. I already bought the t-shirt so I'm really hoping I can make this fly at work. -mjm
From: "Montagne, Michael" <montagne@BOORA.com>
When a table becomes corrupt in Access it is usually easily fixed or replaced from backup as a last resort.
I wish I knew that trick! At my last company we were constantly losing data from Access crashes.
I think PostgreSQL uses seperate files for it's tables so the can be replace if needed.
I thought it was one monolithic file...
What happens if the Zope database gets corrupt?
Check out http://www.zope.org/Members/itamar/CorruptedZODB
It is a monolithic file. Also, what about exporting data for use in a different database or program? Can I read the zope database with ODBC? If I ever needed to convert to another database what about exporting the data?
The great thing about it, is it's Python, so it's simple to write any kind of translator you could imagine.
participants (2)
-
marc lindahl -
Montagne, Michael