JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

the conversion from the IEEE 754 format to the Tandem format when storing the values and from

the Tandem format to the IEEE 754 format when retrieving and passing the values.

Since SQL/MX tables store IEEE 754 floating-point values, JDBC applications accessing floating-point

data do not receive floating-point exceptions. The JDBC applications should check for plus (+) or

minus (-) infinity conditions to determine if an overflow or underflow has occurred. Applications

can also encounter a not-a-number value being passed back, for example, for numbers divided

by zero. This processing is done according to the IEEE 754 standard.

SQL/MP tables can generate floating-point exceptions.

For the range of floating-point values and double-precision values for IEEE 754 format and TNS

format, see the NonStop Server for Java Programmer's Reference. For information on floating-point

formats in SQL/MX, see "Data Types" in the HP NonStop SQL/MX Release 3.2.1 Reference

Manual.

SQL Escape Clauses

JDBC/MX accepts SQL escape clauses and translates them into equivalent SQL/MX clauses, as

shown in the following table:

SQL/MX Equivalent ClauseSQL Escape Clause

DATE 'date-literal'{ d 'date-literal' }

TIME 'time-literal'{ t 'time-literal' }

TIMESTAMP 'timestamp-literal'{ ts 'timestamp-literal' }

join-expression *{ oj join-expression }

INTERVAL sign

{ INTERVAL sign interval-string

interval-string

interval-qualifier }

interval-qualifier

scalar-function{ fn scalar-function }

escape 'escape-character'{ escape 'escape-character' }

CALL procedure-name...{ call procedure-name... }

Not supported in the current release{ ?=call procedure-name... }

* JDBC syntax does not include nested joins, while SQL/MX does.

JDBC/MX extends the SQL escape syntax for an outer join.

JDBC/MX Type 2 Driver Features

The JDBC/MX Type 2 driver supports the following features:

• Row size limit is increased to align with maximum block size 32768 for MX tables.

• A clustering key length up to 2048 bytes is allowed for range and hash partitioned MX tables.

• The precision of the NUMERIC data type is extended up to 128 digits for signed and unsigned

values.

Thread library compliance

The JDBC T2 driver supports NSJ6. When used with NSJ6, the JDBC T2 driver loads the SPT thread

library. No action is required to configure this feature.

JDBC/MX Type 2 Driver Features 73