company logo

Database :: updateMajorVersion - Change time stamp for major version end

The function may be called in order to update version intervals for major versions in case of managed versioning. Each major version for a database has a termination time point, which is also the starting point for the next major version. As long as the termination time for the version lies in the future one may change the version interval by setting a new time stamp as termination time point. The new time stamp must always refer to a time point in future. The function may be called for any kind of managed versioning mode.

The termination time to be set is passed as time stamp in cDateTime.

The major version number to be updated is passed in iVersion. One cannot change the end for the last version, since the last major version has to be an open version, always. The last version will be terminated when creating a new major version (createMajorVersion()), only. When the majorversion number passed in iVersion is not the last but one, the new termination time must not exceed the termination time defined for the next version in the list.

The function throws an exception, when the version number passed in iVersion is not valid, or when the passed time point is invalid. The function also throws an exception, when the versioning mode is not a managed mode.

Implementation details

Database  :: updateMajorVersion ( int32 iVersion, odaba::DateTime &cDateTime )
  • iVersion - Major version number

    Major versions are defined on database level. database versions are numbered consecutively beginning with 0, when consistent versioning has been enabled.

  • cDateTime - Time stamp

    A time stamp combines date and time