<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body>
    Hi,<br>
    <br>
    I remember geogig (formerly geogit) offers promising concepts for
    filebased spatial data management with historization and branching.<br>
    Unfortunately I don't know the current status of the project and the
    progress of integration in QGIS.<br>
    <br>
    Matthias<br>
    <br>
    <div class="moz-cite-prefix">On 07/20/2015 11:25 AM, Neumann,
      Andreas wrote:<br>
    </div>
    <blockquote cite="mid:6ae82f54d0a6ca6b06c1307ab96618da@carto.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <p>Hi Didier,</p>
      <p>I don't think that anyone is working on a client-side
        historisation option in QGIS. And there wasn't much demand for
        that in the past, since most serious GIS data resides in
        databases.</p>
      <p>Andreas</p>
      <p>On 2015-07-20 09:45, didier peeters wrote:</p>
      <blockquote type="cite" style="padding: 0 0.4em; border-left:
        #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
        <div class="">Hello Andreas,</div>
        <div class=""> </div>
        <div class="">yes it's for some 'historisation', more precisely
          to make a filiation, and yes I certainly will use triggers in
          PostGIS.  But I wanted to avoid confusion between different
          kind of edition operations that I'm not currently foreseeing;
          I'm not sure it will always be easy to distinct this specific
          action from others.  And I thought that it might also be
          interesting outside of the database world, to have that "edit
          and preserve" operation. </div>
        <br class="">
        <div class="">
          <div class="" style="color: #000000; letter-spacing: normal;
            orphans: auto; text-align: start; text-indent: 0px;
            text-transform: none; white-space: normal; widows: auto;
            word-spacing: 0px; -webkit-text-stroke-width: 0px;
            word-wrap: break-word; -webkit-nbsp-mode: space;
            -webkit-line-break: after-white-space;">
            <div class="" style="color: #000000; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;">
              <div class="" style="color: #000000; font-family:
                Helvetica; font-style: normal; font-variant: normal;
                font-weight: normal; letter-spacing: normal;
                line-height: normal; orphans: 2; text-align:
                -webkit-auto; text-indent: 0px; text-transform: none;
                white-space: normal; widows: 2; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; word-wrap: break-word;
                -webkit-nbsp-mode: space; -webkit-line-break:
                after-white-space;">
                <div class="" style="color: #000000; font-family:
                  Helvetica; font-style: normal; font-variant: normal;
                  font-weight: normal; letter-spacing: normal;
                  line-height: normal; orphans: 2; text-align:
                  -webkit-auto; text-indent: 0px; text-transform: none;
                  white-space: normal; widows: 2; word-spacing: 0px;
                  -webkit-text-stroke-width: 0px; word-wrap: break-word;
                  -webkit-nbsp-mode: space; -webkit-line-break:
                  after-white-space;">
                  <div class="" style="color: #000000; font-family:
                    Helvetica; font-style: normal; font-variant: normal;
                    font-weight: normal; letter-spacing: normal;
                    line-height: normal; orphans: 2; text-align:
                    -webkit-auto; text-indent: 0px; text-transform:
                    none; white-space: normal; widows: 2; word-spacing:
                    0px; -webkit-text-stroke-width: 0px; word-wrap:
                    break-word; -webkit-nbsp-mode: space;
                    -webkit-line-break: after-white-space;"><span
                      class="Apple-style-span" style="border-collapse:
                      separate; color: #000000; font-family: Helvetica;
                      font-style: normal; font-variant: normal;
                      font-weight: normal; letter-spacing: normal;
                      line-height: normal; orphans: 2; text-align:
                      -webkit-auto; text-indent: 0px; text-transform:
                      none; white-space: normal; widows: 2;
                      word-spacing: 0px; border-spacing: 0px;
                      -webkit-text-decorations-in-effect: none;
                      -webkit-text-stroke-width: 0px;">Didier<br
                        class="">
                    </span></div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br class="">
        <div>
          <blockquote class="">
            <div class="">Le 20 juil. 2015 à 09:10, Neumann, Andreas
              <<a moz-do-not-send="true" class=""
                href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>>
              a écrit :</div>
            <div class="">
              <div class="" style="font-size: 10pt; font-family:
                Verdana,Geneva,sans-serif;">
                <p class="">Hi Didier,</p>
                <p class="">Is this for historisation purposes? If yes,
                  I would look into database solutions to do
                  historization.</p>
                <p class="">The SQL-MM standard has this as a built-in
                  tool set for databases, however, PostgreSQL does not
                  implement this part of the SQL specification (I
                  believe the latest versions of SQL server and Oracle
                  12 does). However, you can simulate the same in
                  Postgis, using triggers and rules.</p>
                <p class="">Andreas</p>
                <p class="">On 2015-07-20 08:00, didier peeters wrote:</p>
                <blockquote class="" style="padding: 0 0.4em;
                  border-left: #1010ff 2px solid; margin: 0;"><!-- node type 8 --><!-- node type 8 --><!-- node type 8 -->Hello,
                  <div class=""> </div>
                  <div class="">I would like to find the best solution
                    to the following case:</div>
                  <div class=""> </div>
                  <div class="">in QGis, when editing a polygon
                    (splitting it in 2 parts) I need to save the
                    original shape, in order to keep the different steps
                    of its evolution; this operation is likely to be
                    repeated several times.  The solution I found is to </div>
                  <div class="">
                    <ul class="MailOutline">
                      <li class="">start by copying the polygon, </li>
                      <li class="">then edit it (split) </li>
                      <li class="">then pasting back the original one, </li>
                      <li class="">then adjust and update the attributes
                        of the 2 new polygons.  </li>
                    </ul>
                    <div class=""> </div>
                  </div>
                  <div class="">Is there a less tricky way to achieve
                    this ?  </div>
                  <div class=""> </div>
                  <div class="">If not it would be nice to have an
                    option in the save dialog (with a default behaviour
                    set in the Settings), and I would file a feature
                    request.  </div>
                  <div class=""> </div>
                  <div class="">Didier</div>
                  <!-- node type 8 --><br class="">
                  <div class="pre" style="margin: 0; padding: 0;
                    font-family: monospace;">_______________________________________________<br
                      class="">
                    Qgis-user mailing list<br class="">
                    <a moz-do-not-send="true" class=""
                      href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br
                      class="">
                    <a moz-do-not-send="true" class=""
                      href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></div>
                </blockquote>
                <div class=""> </div>
                <div class=""> </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br class="">
        <!-- html ignored --><br>
        <div class="pre" style="margin: 0; padding: 0; font-family:
          monospace">_______________________________________________<br>
          Qgis-user mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br>
          <a moz-do-not-send="true"
            href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></div>
      </blockquote>
      <p> </p>
      <div> </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
    </blockquote>
    <br>
  </body>
</html>