[Project] Blog entry on opt-in versioning
This commit is contained in:
parent
e0bd53b001
commit
62945aeddc
|
@ -56,6 +56,33 @@
|
||||||
<!-- blog items -->
|
<!-- blog items -->
|
||||||
<div class="col-sm-8 blog-main">
|
<div class="col-sm-8 blog-main">
|
||||||
|
|
||||||
|
<!-- blog post -->
|
||||||
|
<div class="blog-post">
|
||||||
|
<h2 class="blog-post-title">Versioning of objects</h2>
|
||||||
|
|
||||||
|
<p class="blog-post-meta">8. August, 2016 by <a href="#">Robert</a></p>
|
||||||
|
|
||||||
|
<p>Opt-In versioning of objects</p>
|
||||||
|
<hr>
|
||||||
|
<p>A major new feature has landed in Strolch. Now, using opt-in, it is possible to have all changes to
|
||||||
|
the object model be versioned. This means that any change to <code>Order</code>,
|
||||||
|
<code>Resource</code> or <code>Activity</code> is automatically versioned and one can then revert to
|
||||||
|
this version later on.</p>
|
||||||
|
|
||||||
|
<p>This will make it far easier to implement undo operations in applications since it is an inherent
|
||||||
|
part of the lifecycle of objects in Strolch.</p>
|
||||||
|
|
||||||
|
<p>Since Strolch is supposed to be used also in small footprint hardware, this option is opt-in.</p>
|
||||||
|
|
||||||
|
<p>A side affect of this new feature is that we have for the time being not ported the XML persistence
|
||||||
|
layer. If this is required, then someone drop us a note and we'll check on it.</p>
|
||||||
|
|
||||||
|
<p>So now go ahead and add <code><enableVersioning>true</enableVersioning></code> to your
|
||||||
|
Realm so that versioning is enabled.</p>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<!-- /.blog-post -->
|
||||||
|
|
||||||
<!-- blog post -->
|
<!-- blog post -->
|
||||||
<div class="blog-post">
|
<div class="blog-post">
|
||||||
<h2 class="blog-post-title">Release 1.2.0</h2>
|
<h2 class="blog-post-title">Release 1.2.0</h2>
|
||||||
|
|
Loading…
Reference in New Issue