For a service management/inventory/provisioning application I once wrote, I used timestamps for version numbers on all principle records. I also kept a log of committer, comments and an automated overview expression of the change.

As you suggest, I had views that presented current state and others that presented the full history. It was simple (crude even) but surprisingly effective. So much so and so subtly/profoundly so that several attempts to replace it through the years were aborted when they realized the replacements weren't as helpful as the original. It was all Perl/PostgreSQL - no triggers or stored procedures. A real developer (I'm just a sysadmin) who supported it after I left said it was very easy to understand but I was obviously not a developer because I hadn't used any of the tools that would have made it easier. But I ramble...

I have often wished for the structure of a relational database with the version/update history of repositories like cvs and git. I wish I could add a time or version to my queries to pull out the way it was. The concept is simple but I have never seen anything like it or made it myself. But then I haven't put much effort into finding such a system.

In reply to Re: database historisation by ig
in thread database historisation by morgon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.