Databases
StackOverflow2013
Postsdbo
POObject versioning patterns
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POObject versioning patterns
    primarykey
    data
    text
    <p>I'm trying to model some of our objects in our domain and came across a problem that some of these objects could be versioned. i.e, user could create new object versions over a period of time. So, I need to model them in the program. I think that this is a common problem in SW design. </p> <p>Initially I jumped to the idea of mimicing source control versioning concepts and came up with a versioned object concept and methods like check-in, check-out etc. But, I get a feeling that it is not quite 'systematic' as I didn't explore patterns (i.e, I feel like committing sins like </p> <ul> <li>I didn't cover aspects like looking for more than one solution </li> <li>looking into literature which would give me more solid references etc). </li> </ul> <p>So, my current problem is that for a systematic modelling, I need to search for patterns which addresses the version modelling problem, preferrably in literature. And take the best out of it, of course.</p> <p>So, I googled for such patterns and only found a <a href="http://martinfowler.com/eaaDev/TemporalObject.html" rel="noreferrer">Temporal Object pattern</a>. But, I was not sure if this was really what I wanted. Do you guys have any suggestion on such patterns?</p> <p>[Self-Edit] Maybe I haven't described the problem well. You can see the problem similar to a source-control file-versioning problem. I have several types of objects (stored in database) that can have several versions. Inside my application I have to handle all these versions and also I will have to create new version of objects (which will eventually get stored in database). What I'm looking forward is some kind of cite-able pattern with which I can model the interfaces for accessing/modifying/adding new versions for these objects. The basic interface I could come up with is IVersionedObject with methods like checkout, checkin, undoCheckout etc. But, this is my own idea observing source control systems. I don't thing it is a SW design pattern as such. So, looking forward for some very well documented design patterns for the above problem.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPermanentGuest
    1. USPermanentGuest
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POObject versioning patterns
      1. USranendra
      1. VTFavorite
    2. VO
      singulars
      1. POObject versioning patterns
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POObject versioning patterns
      1. This table or related slice is empty.
      1. VTUpMod
    1. COcheck this http://stackoverflow.com/questions/557570/what-versioning-design-pattern-would-you-recommend it may give you an idea
      singulars
      1. POObject versioning patterns
      1. USAmir Ismail
    2. COYou can check this [post](http://miroprocessordev.blogspot.com/2011/11/design-patterns-series-1-introduction.html) for various design patterns
      singulars
      1. POObject versioning patterns
      1. USAmir Ismail
    3. COthanls Amir Ismail for the stackoverflow link. This had some helpful links, but not enough for a solution :-(
      singulars
      1. POObject versioning patterns
      1. USPermanentGuest
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload