6

Is there a common name for the practice of keeping a version number on your data, so that different versions of your program can identify, for example, "current", "legacy", and "too-old-to-deal-with" versions of the same type of object?

As discussed here: Strategy for backwards compatibility of persistent storage.

Improve this question
3
  • 1
    ... versioning? Commented Aug 22, 2012 at 10:16
  • That might just be it. I was wondering if there was a more specific term. Commented Aug 22, 2012 at 13:58
  • Depends on the type of versioning being used. The "version" column of a database record is more for concurrency than backward-compatibility. For files, I'd probably call it "file version compatibility" Commented Aug 22, 2012 at 17:44

2 Answers 2

Reset to default
1

Since version control systems handle continuously changing versions of document objects, perhaps their nomenclature is appropriate.

  • Subversion: revision
  • Git: changeset (or perhaps commit)

In both cases this is metadata associated with the underlying object, and is usually a pointer to a linked list of other pointers representing the history.

So, it would seem that the term you're looking for is the name given to the "collection of revision history pointers" which would be "revision history".

Improve this answer
0

When used with databases, the term I run into the most is

(Database) Schema Version Number

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.