BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4


4040 Linz, Austria

What is meant by "Versioning on row level"?

Versioning on row level

Another alternative to maintain tables from relational databases is versioning on row level.

To save data chronological and/or retain the change history in a RDB, versioning on row level can be used.

Technical fields, that are needed for that feature, must be integrated into the table structure. The original table structure, respectively sights of the table (e.g. the rows valid at a specified date), are mapped as views.

The minimal mode of operation is versioning without change history with valid-from-date as last key field, and with deletion mark. Another mode of operation with history additionally includes a time stamp field in the key. As an alternative to the deletion mark, a valid-until-date can be used.

The advantage of this storage mode is that the whole history of data is centrally saved in a RDB and no auxiliary tables are needed.

fig. Example for versioning on row level



Changes in ESA data spaces, efficient migration and a new success story: Learn more in our newsletter!


Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.


» Migration Packages

Success Stories

GDIS and BOI: Carrying on the Success

With TABEX4 JTC, GDIS has introduced the world's fastest Java interface for table access on customer and control data. Learn the details in our new Success Story.


» read this Success Story

» read more Success Stories