On Thu, 15 Apr 2004 20:40:09 -0400 (EDT)
Shane Hathaway <[EMAIL PROTECTED]> wrote:

> On Wed, 14 Apr 2004, Kapil Thangavelu wrote:
> > although i wonder if there is some hand waving in progress here that
> > i can't see. i guess my semantic notion of versions has been that of
> > long lived transactions, and is there a better means of thinking of
> > them? how do they play across with multiple mounted zodbs? what
> > would something like merge mean in the context of a catalog?
> By my understanding, outside the storage, different versions are
> completely independent.  You could even simulate multiple databases
> using versions.  It is the storage that knows how to create new
> versions, merge versions, and prevent objects being used in a version
> from being changed.
> Mounted databases try to use the same version as the root connection.
> To merge a catalog, you could bring one of the stored catalogs to life
> within the storage and replay the sequence of transactions that
> occurred in the other catalog.  This could be tricky, and opening a
> catalog within a ZEO server would make the ZEO server less stable.

Ok, running the catalog on the storage server. Now that's crazy talk ;^)

running-awayly y'rs,


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to