SQL/MP Version Management Guide

Database Versions
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
3-15
Object-Version Dependencies
For example, by entering the following command at the SQLCI prompt, you can execute
FILEINFO to determine the version of the collation named COLL1:
>> VOLUME \SYS2.$VOL1.SALES;
>> FILEINFO COLL1, DETAIL;
The response to this command is:
\SYS2.$VOL1.SALES.COLL115 July 1994, 15:00
SQL CHARACTER PROCESSING RULES OBJECT
CATALOG $VOL1.SALES
VERSION 300
TYPE K
.
.
In the preceding example, the FILEINFO command reveals that the version number of
the COLL1 collation is 300.
For more examples and for information on using this utility, see the NonStop SQL/MP
Reference Manual.
Object-Version Dependencies
The versions of SQL objects are interrelated; the version of one object might depend on
the version of related objects. For example, suppose you have a version 2 table with a
version 2 protection view on it. Adding a version 300 constraint to the table raises both
the table’s version and the protection view’s version to 300.
This table summarizes the object-version dependencies between the types of SQL
objects supported in version 300 and newer. In this table, a view is either a protection
view or a shorthand view.
The basic rule for object-version dependency is that the dependent version can be newer
than the parent version, but not older. The following conventions determine how
SQL/MP determines object-version dependency for particular objects:
Parent Version Dependent Version
Underlying table version
Underlying view version
View version
Index version Base table version
Constraint version Base table version
Collection version Index version
Table version
View version
Note. Do not confuse object-version dependency with object dependency. An index or a
constraint depends on a base table for its existence; this is object dependency. The version of
a table depends on the version of any indexes, constraints, or collations associated with the
table; this is object-version dependency.