Versions are problematic in combination with mounted storages in particular because there is no link in versioning between storages. You can easily create a versioned object in one storage, then traverse to another part of the instance space that's been mounted and use that version cookie to make a change. But you need to commit the two versions separately. If you commit one of them, you'll be left scratching your head as to why the other storage didn't commit. I'd say in this particular that it's perhaps a limitation of mounted storages rather than versions.

-----Original Message----- From: Chris Withers [mailto:chrisw@nipltd.com] Sent: Wednesday, August 30, 2000 8:28 AM To: Chris McDonough Cc: 'Roman Milner'; zope@zope.org Subject: [Zope] Versions...

Chris McDonough wrote:

...

Mounted storages fall down with versions (do not use versions in conjunction with mounted storages, it will do bad things to you).

Is it just me or are versions not exactly the most robust things around?

(I'm thinking external methods here, and ftp access into a version, amongst others ;-)

cheers,

Chris

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )