US 2024/0256255 A1 · DOWNGRADING DATABASE SOFTWARE

Abstract

Techniques for downgrading of database software. Code areas that may affect downgradability may be delineated with code markers. Changes to these sections can be made to prevent a new database version from being built unless a process is taken to indicate that any new features be designated as available, but not yet allowed for N software releases. This provides a downgrade window of N releases that will support functionality currently allowed by the database. In response to receiving a downgrade request to a target older database software version, that request can be permitted if all the database features are available or allowed in the target version. If at least one of the database features is not available in the target version, the downgrade requested is not permitted. If the request is permitted, the downgrade operation is commenced.

Claims20

Dependent claims

A non-transitory, computer-readable medium storing program instructions that are capable of being executed on a computer system to perform operations that comprise:

receiving a request to downgrade from a current version of database software to an older, target version of database software, the database software being executable to interface with a database;
performing a downgradability test that determines whether the target version of the database software is compatible with a current state of the database, wherein the performing includes:
determining a first set of features that have been allowed for the database;
determining a second set of features that are indicated as available or allowed in the target version of the database;
determining whether the target version of the database software is compatible with a current state of the database by assessing whether all of the first set of features are included in the second set of features;
and
responding to the request based on a result of the downgradability test.

4 more elements

A computer-implemented method, comprising:

detecting a code change to a downgrade-sensitive portion of code of database software that is executable to interface with a database, wherein a new feature corresponding to the code change replaces an old feature;
in response to detecting the code change, preventing a build of a release of the database software until the new feature is registered as having an available state;
in response to the new feature being registered as available, building the next N versions of the database software to:
include a first code portion implementing the old feature and a second code portion implementing the new feature;
and
enable the first code portion, but not the second code portion;
after N versions of the database software that include new feature, changing registration of the new feature from the available state to an allowed state such that successive versions of the database software are built to enable the second code portion, but not the first code portion;
receiving a request to downgrade from a current version of database software to an older, target version of database software;
determining whether to permit the request based on whether a first set of features that have been allowed for the database are indicated as either available or allowed in a second set of features corresponding to the target version of the database software;
and
responding to the request based on the determining.

8 more elements

Dependencies are inferred from the claim text.

Downgrading database software

Life of this patent

Downgrading database software

Life of this patent

Abstract

Claims20