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-11
Interoperability across schema versions
compiled the module. The SQL/MX Release 3.1 compiler produces the module version
3100.
For a module to be executed on a node, the module version must be higher than or
equal to the earliest supported plan version and lower than or equal to the current plan
version. Otherwise, SQL/MX generates a versioning error.
Interoperability across schema versions
NonStop SQL/MX Release 3.1 is compatible with v1200 schemas, v3000 schemas,
v3100 schemas, and the objects in such schemas on the local node and on remote
compatible nodes in a network.
Limitations to schema version interoperability

Schemas of different versions cannot coexist in the same catalog.

Immediately after upgrading from SQL/MX Release 2.3.x or from SQL/MX Release
3.0 to SQL/MX Release 3.1, the version of the system schema and all user
schemas is either 1200 or 3000. Executing the
UPGRADE ALL METADATA
command will upgrade all metadata for the system schema and the user schemas
to v3100. After the metadata is upgraded to v3100, you cannot create v1200
schemas. However, using the
control query default (cqd) command, you
can create v3000 schemas in catalogs that do not already contain v3100 schemas:
control query default create_definition_schema_version '3000'

Database relationships cannot cross schema versions.
For example, a view in a v1200 schema cannot reference a table in a v3100
schema.
The following types of database objects are able to establish cross schema
relationships:

views

triggers

RI constraints
If you attempt to establish cross-schema relationships between schemas of
different versions, the attempt will be rejected and an error is generated.
Note. SQL/MX Release 3.1 supports v3100 and v3000 plans and modules. However, it does
not support SQL/MX Release 2.3.x plans and modules. Before executing SQL/MX Release
2.3.x plans and modules on SQL/MX Release 3.1, you must recompile them.