SQL/MX 3.2.1 Installation and Upgrade Guide (H06.26+, J06.15+)

New features in SQL/MX Release 3.2
SQL/MX Release 3.2 introduces the following features:
• Similarity Check for Views
• Subqueries in WHEN clause for AFTER triggers
• Calling SPJs from Triggers
For more information on the new features, see the SQL/MX Reference Manual.
After upgrading to SQL/MX Release 3.2.x, you can use the new features on your 3.2.x database
and new applications. You can also use the new features on older databases and applications.
In this scenario, you must upgrade the metadata in affected catalog to use the new features.
Considerations for using the Similarity Check feature
You must consider the following factors before using the Similarity Check feature:
• The DDL_VIEW_SIMILARITY_CHECK defaults attribute is set to ENABLE, by default. In
SQL/MX Release 3.2.x, if you create a view on a schema with version 1200, 3000, or 3100,
a version-related error is returned. You must set the default attribute to OFF before creating a
view on schemas with a version earlier than 3200.
• If you perform a metadata upgrade on a schema with version 1200, 3000, or 3100 that
contains views, DISABLE SIMILARITY CHECK is added to the view text, and appears in
the SHOWDDL output.
New features in SQL/MX Release 3.2.1
SQL/MX Release 3.2.1 introduces the following features:
• Sequence generator support
• 64–bit support in dynamic SQL
After upgrading to SQL/MX Release 3.2.1, you can use the new features on your 3.2.1 database
and new applications. You can also use the new features on older databases and applications.
In this scenario, you must upgrade the metadata in the affected catalog to use the new features.
Implementing the new functionality
If there is a chance of falling back to an earlier version, you must defer the implementation of the
new functionality until you are sure that fallback is unlikely.
36 Considerations for upgrading the system to SQL/MX Release 3.2.x