SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Considerations for upgrading to SQL/MX Release
3.0
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
2-7
Working with v3000 and v1200 objects in
SQL/MX Release 3.0
In SQL/MX Release 3.0, a catalog does not have an explicit version. A catalog can
contain either v1200 or v3000 schemas, but not both.
A CREATE SCHEMA statement will create a new schema of the same version as
those in the catalog. By default, schemas created in new catalogs will be v3000. You
need not take any explicit action to create or maintain v3000 objects. Until the
UPGRADE ALL METADATA command is issued to force all existing metadata to
v3000, you can continue to create and maintain v1200 schemas and their contained
objects. Explicit action is needed only when a v1200 schema is required in a new
catalog that does not already contain v1200 or v3000 schemas. To create a v1200
schema, you must enter the following
control query default command:
control query default create_definition_schema_version '1200'
For more information on commands, see MXCI Commands in the SQL/MX Reference
Manual
.
Conversions from numeric to char or varchar
SQL/MX Release 3.0 is ANSI-compliant and reports 8402 errors during conversions
from numeric to char or varchar types with truncation. In SQL/MX Release 2.x, such
conversions truncate the data without any errors.
The following examples illustrate overflow errors generated in SQL/MX Release 3.0:
Figure 2-9. Coexistence of new and old databases
App1
V1200
App2
cat2
sch2
V3000
App3
cat1
sch1