SQL/MX 3.2.1 Programming Manual for C and COBOL (H06.26+, J06.15+)

Name Resolution, Similarity Checks, and Automatic
Recompilation
HP NonStop SQL/MX Release 3.2.1 Programming Manual for C and COBOL—663854-005
8-13
Similarity Check

The query must not use compound statements.

ESP parallelism must not have been used.

The query must not include any SQL/MP views.

A CALL statement must not refer to a stored procedure in Java (SPJ) that has
been dropped and re-created in NonStop SQL/MX.

An IUD query must not be an embedded update or delete.

The query must not be an update on primary key or unique index column.
Similarity Check Criteria for a View
During similarity check for a view, the SQL/MX executor compares the view at compile-
time and run-time. For the view to pass the similarity check, the following criteria must
be satisfied:

The view text, except for the table name and view name, must remain the same.

The view must not be a nested view or a view with VALUES clause.

Similarity check for views must be enabled for all the views referred to in the DML
statement.

The number of view columns must be the same between compile-time and run-
time.

The following attributes must be the same for all the corresponding columns
projected by the views:

Name

Heading

Data type

Character Set

Collation

NULL/NOT NULL

IDENTITY COLUMN.

The tables referred by both the views must pass the Similarity Check Criteria for
tables. If any of the criteria is not fulfilled, similarity check for views fails. A warning
is issued If the RECOMPILATION_WARNINGS CQD is set to ON.