[ZDP] BackTalk to Document The Zope Book (2.5 Edition)/Using Basic Zope Objects

[webmaster@zope.org]

A comment to the paragraph below was recently added via http://www.zope.org/Documentation/Books/ZopeBook/current/BasicObject.stx#3-247

---------------

      ZCatalog has a way of connecting changes made to disparate
      objects. This is because cataloging an object must, by necessity
      change the catalog. Objects that automatically catalog
      themselves when they are changed propigate their changes to the
      catalog. If such an object is changed in a version, then the
      catalog is changed in the version too, thus locking the
      catalog. This property makes the catalog and versions get along
      poorly.  As a rule, versions should not be used in applications
      that use the catalog.

        % Anonymous User - May 29, 2002 12:08 pm:
         `propagate'

        % Anonymous User - Sep. 21, 2002 5:56 pm:
         Again: what is the advantage of using Version against working on a copy and finally overwriting original?

        % Anonymous User - Sep. 25, 2002 3:26 pm:
         While this could work if you were editing some of the content of your site, just think of how it would work
         if you were indeed working on the menu of the site. You could work on something called menu_copy or new_menu,
         but then, how to test it? All the pages in your site still use the original menu, so you can't really test
         your menu.
         Using versions allows you to test new code and templates and to see how they affect the whole site. You (and
         the person that work with you on that version) are the only ones that see the new site, while your users
         still enjoy the old one.