Troy Farrell wrote:
What's bothersome is how it is not working. If versions are really a problem, they should be removed until they work and are not causing data loss. We shouldn't say that Zope can do versionning, but don't use it because you might loose data. Perhaps one of the versions gurus has some insight for us.
IANVG, but I can tell you that versions as implemented in zope (2.3.3) are evil. They are totally uncontrollable by permissions, since they just depend on the client sending a certain cookie, without even checking if the corespondending Version object even exists (text book example for the violation of the "never trust the client" principle). At least it was this way in 2.3.3, and I doubt anything has changed since then. Therefore, even if that database corruption bug is fixed, I'd like to see at least the possibility to completly turn off the version _functionality_ (i.e. said cookie is ignored instead of causing an change of an object getting versioned). cheers, oliver