SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

Considerations for upgrading to SQL/MX Release
3.1
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
2-5
New features in SQL/MX Release 3.1
Value:123456789012345678 to Target
Type:VARCHAR(REC_BYTE_V_ASCII).
--- 0 row(s) selected.
>>
>>select cast(a * a as char(18)) from tnumeric;
(EXPR)
------------------
9.000000000000
*** ERROR[8402] A string overflow occurred during the
evaluation of a character expression. Conversion of Source
Type:DECIMAL SIGNED(REC_DECIMAL_LSE) Source
Value:0x2B000105020401050708070503020308080306050207090608020
909070605020709060804 to Target Type:CHAR(REC_BYTE_F_ASCII).
--- 1 row(s) selected.
>>
>>update tnumeric set a = a + a
+>where cast( a * 20 as char (10)) > '5';
*** ERROR[8402] A string overflow occurred during the
evaluation of a character expression. Conversion of Source
Type:DECIMAL SIGNED(REC_DECIMAL_LSE) Source
Value:0x2B0002040609010305070800020406090103050600 to Target
Type:CHAR(REC_BYTE_F_ASCII).
--- 0 row(s) updated.
>>
New features in SQL/MX Release 3.1
SQL/MX Release 3.1 introduces the following new database features:

Inclusion of IDENTITY columns in tables

Capability to change the ownership of database objects

Capability to restrict catalog and schema creation to predefined set of users

Capability to define security administrators who can manage access to database
objects without having explicit access to the data in those objects.
For more information on the new features, see the SQL/MX Release 3.1 Reference
Manual.
After upgrading to SQL/MX Release 3.1, you can use the new features on databases
and applications created . You can also use the new features on older databases and
applications, however, you must upgrade all the metadata before using them.