SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

Version management and interoperability
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
3-10
SQL/MX query plan and module versions
Displaying the OSV and OFV
The following example displays the OSV and OFV of a specified database object,
where the table name,
tlarge, is a value that you specify:
>>get version of table tlarge;
OBJECT SCHEMA VERSION: 3100
OBJECT FEATURE VERSION: 3100
--- SQL operation complete.
>>
The following is an example of feature_version_info function:
>>select object_name, feature_version
from table (feature_version_info ('CATALOG', 'CATX', 1200));
OBJECT_NAME FEATURE_VERSION
-------------------------------------- ---------------
CATX."schema x"."table with large key" 3100
CATX.SCHEMAY."table with bignum column" 3100
FEATURE_VERSION_INFO is a built-in table-valued function that returns feature
version information for all user objects with an OFV higher than a given value, in a
specified set of catalogs.
The MXCI SHOWLABEL command also displays OSV and the OFV.
SQL/MX query plan and module versions
Query plan versioning is a set of mechanisms that allow SQL/MX software to assign a
version to query execution plans and modules and to determine if the version of a
query execution plan or module is compatible with the MXV. Query plan versions
include the plan version and module version.
Plan versions
The query execution plan of a SQL statement is assigned a plan version depending on
the SQL/MX release that is installed on the node where the plan is compiled.
NonStop SQL/MX successfully compiles and executes a query execution plan if the
plan version is higher than or equal to the earliest supported plan version and lower
than or equal to the current plan version of the node where the plan is being executed.
Otherwise, NonStop SQL/MX returns a versioning error.
Module versions
When you compile modules of embedded SQL/MX applications, the version assigned
to a module is the same as the default compiler version of the node where you