UniverseUniversity


Home Projects Jobs Clientele Contact

uu


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Versioning




Alexey Parshin wrote:
>
>
> 2006/10/21, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com
> <mailto:ilya@total-knowledge.com>>:
>
>     Alexey Parshin wrote:
>     > I'm not talking about the complete functionality yet. The schema I
>     > described allows to implement it, but at the moment I'm only
>     trying to
>     > develop a way of switching the versions.
>     > The main questions at the moment, I guess, are:
>     > 1) how do we keep object versions to track the version tree. I've
>     > offered a conception of original object..
>     How about (from logical standpoint, don't know about db) making
>     object
>     identified a composite: object number + object version?
>     The combo has to be unique, but not its elements.
>
>
> Ok with me.
>
>     Then version information will be carried along with any object
>     reference.
>
>
> Ok.
>
>     > 2) what do we do when the new version is produced. My idea is - to
>     > switch all the object connections to that new version ( edit) or to
>     > produce a new version disconnected, to be used in another parent
>     > object (clone).
>     From http://www.total-knowledge.com/wiki/index.php/UU_Tech
>
>     When a new version is created, all objects linking to this one are
>     notified. Their action can be one of the following:
>
>         * Silently use new version
>         * Use new version and notify owner
>         * Notify owner and keep old version
>         * Silently stick with old version
>
>
> Then we need that flag in the original object, or even in every object.
Umm... No - in every reference. It is particular reference that defines "New
version" action.
Example:
I have a topic. You have an explanation that I included. I decide what I
want to happen when you create new version.
>
>     > 3) we may also have a reference to the particular version, original
>     > version, or latest version. This part can be discussed after we now
>     > answers to 1) and 2)
>     >
>     > 2006/10/21, Ilya A. Volynets-Evenbakh < ilya@total-knowledge.com
>     <mailto:ilya@total-knowledge.com>
>     > <mailto:ilya@total-knowledge.com
>     <mailto:ilya@total-knowledge.com>>>:
>     >
>     >     I'm not sure that what you described gives us same
>     functionality
>     >     as we need
>     >     (http://www.total-knowledge.com/wiki/index.php/UU_Tech has
>     >     quick spec.)
>     >
>     >     Alexey Parshin wrote:
>     >     > There are several ways to do versioning.
>     >     >
>     >     > Here is one:
>     >     >
>     >     > Every object should have a version number, a reference to
>     an object
>     >     > it's derived from (previous version), and a reference to the
>     >     original
>     >     > object. The separate table should hold object class,
>     original object
>     >     > id, and the latest version of that object available.
>     >     >
>     >     > The question is how to indicate the latest version of the
>     >     object. We
>     >     > can move the connections of the old version to the new
>     version,
>     >     if the
>     >     > new version stays with the same parent object. If we need to
>     >     step back
>     >     > to prior version - we just switch connections to required
>     >     version. All
>     >     > the versions have the same original object id reference.
>     >     >
>     >     > 2006/10/20, Ilya A. Volynets-Evenbakh <
>     ilya@total-knowledge.com <mailto:ilya@total-knowledge.com>
>     >     <mailto:ilya@total-knowledge.com
>     <mailto:ilya@total-knowledge.com>>
>     >     > <mailto: ilya@total-knowledge.com
>     <mailto:ilya@total-knowledge.com>
>     >     <mailto:ilya@total-knowledge.com
>     <mailto:ilya@total-knowledge.com>>>>:
>     >     >
>     >     >     Few more things, at we are going to be in good enough
>     shape to
>     >     >     start writing stored procs
>     >     >     - I don't see where student's solution of a problem is
>     stored
>     >     >     - Versioning support
>     >     >     - DoT doesn't look too close to what I was thinking, but
>     >     I'll leave
>     >     >       it alone till I know what it really should be
>     working like.
>     >     >
>     >     >     Probably there are other things I missed, so we'll change
>     >     >     schema later as needed.
>     >     >
>     >     >     --
>     >     >     Ilya A. Volynets-Evenbakh
>     >     >     Total Knowledge. CTO
>     >     >     http://www.total-knowledge.com
>     <http://www.total-knowledge.com>
>     >     >
>     >     >
>     >     >
>     >     >
>     >     > --
>     >     > Alexey Parshin,
>     >     > http://www.sptk.net
>     >
>     >     --
>     >     Ilya A. Volynets-Evenbakh
>     >     Total Knowledge. CTO
>     >     http://www.total-knowledge.com
>     >
>     >
>     >
>     >
>     > --
>     > Alexey Parshin,
>     > http://www.sptk.net
>
>     --
>     Ilya A. Volynets-Evenbakh
>     Total Knowledge. CTO
>     http://www.total-knowledge.com
>
>
>
>
> -- 
> Alexey Parshin,
> http://www.sptk.net 

-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com


Authoright © Total Knowledge: 2001-2008