Version Control

Version control was introduced to the GAM database on 21 May 2021 in order to

• keep track of the changes to the GAM database
• ensure the correct interplay between the GAM database and the software tools that make use of the GAM database.

The major GAM database version number MUST be the same for the GAM database and any program that is using the GAM database. The minor version number indicates minor changes which might not be relevant for all programs acessing the GAM database. So for most Helium Management applications there is just a minimum minor version number requested. For example a Helium Management application requires a GAM database version 1.0 (i.e. major.minor) and would be able to work flawlessly with versions 1.1 and 1.2 .

Version control table

Attribute name	Attribute meaning	Data type	Mandatory	Notes
VER_ID	ID of version / update	24-bit Integer	Yes	It is the primary key. It is automatically incremented, no need to set it manually.
VER_MAJOR	Major version number	24-bit Integer	Yes	With the implementation of the version control the version is set to 1.0
VER_MINOR	Minor version number	24-bit Integer	Yes
VER_DATE	Date and time of the installation of the version / update	String showing date in YYYY-MM-DD hh:mm:ss format	Yes
VER_COMMENT	Comments related to this version / update	String, up to 1000 bytes in size	No	This field may contain any information about the version / update and possibly who installed the version / update.