SQL/MP Version Management Guide
Overview of Version Management
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
1-5
Object Version
corresponds to the oldest version of SQL/MP software that can read from or write to the
catalog.
A catalog format version number, unlike a catalog version number, is based on the
physical structure of an SQL user or system catalog. Therefore, it changes only when the
structure of a catalog changes.
A new catalog format version number is assigned when the physical structure of an SQL
catalog changes; for example, when a new catalog table is added, a new column is added
to an existing table, or an existing column is modified to accept values it could not
accept before.
When a catalog is assigned a new catalog format version number, it is also assigned a
new catalog version number. Because the catalog format version number does not
always change when its corresponding catalog version number changes, the catalog
format version number is always equal to or less than its corresponding catalog version
number.
Object Version
An object version number is a version number assigned to SQL objects: tables, indexes,
views, collations, and constraints. The object version number of an object is determined
by the features associated with the object. For example, collations were introduced with
version 300 of the SQL software, so a collation is at least a version 300 object;
conversely, because no new object features were introduced with version 315, an object
cannot be version 315.
Message File Version
A message file version number is a version number assigned to a message file: a file that
contains the error, warning, informational, and help text messages issued by SQL/MP.
The message file version of a SQL/MP message file does not have to be the same as the
version of SQL/MP software with which the message file is used. This flexibility allows
messages to be added or changed between releases of SQL/MP.
Program Format Version and Program Catalog Versions
Two kinds of version numbers are assigned to SQL/MP programs: program format
versions (PFVs) and program catalog versions (PCVs).
A program format version (PFV) identifies the minimum version of the SQL executor
needed to execute a program. The PFV assigned to a program is determined by the
version of the SQL compiler used to SQL-compile the program.
The PFV of a program is related to features in the SQL/MP software. For example,
because collations were introduced with version 300 of the SQL software, an SQL
compiler with a program format version of at least 300 is needed to compile a program
that uses collations.
A program catalog version (PCV) identifies the oldest version of the catalog in which a
program can be registered. A program’s PCV is determined by the SQL/MP features