Comply with SQLJ
The syntax of Java™ UDRs
that the HCL OneDB™ database
server supports usually follows the SQLJ specification. Where syntactic
differences and missing features occur, the differences are mostly
due to differences between HCL
OneDB SQL
and the SQL-3 standards. The following table summarizes the level
of SQLJ compliance.
| Feature (SQLJ section #) | Function | Syntax | Definition and rules | Comments |
|---|---|---|---|---|
| jar names (3.1) | Yes | Yes | Yes | |
| Java path (3.2) | Yes | Yes | Yes | |
| Install, replace, or remove JAR files (4.1-4.3) | Yes | Yes | Yes (required) No (optional) | No support of the optional replacement jar validation rules. |
| Alter Java path (4.4) | Yes | Yes | Yes | |
| Create procedure, Create function (5.1)1 | Yes | Yes | Yes (required) No (optional) | No support of the optional create time jar validation and the Java main method. |
| Drop procedure, Drop function (5.2) | Yes | Yes | Yes | |
| Grant or revoke jar (5.3-5.4, optional) | No | No | No | |
| SQLJ function call (5.5) | Yes | Yes | Yes | |
| SQLJ procedure call (5.6) | Yes | Yes | Yes | |
| System properties and default connections | No | No | No | |
| Deployment- descriptor files (optional) | Yes | No | No | |
| Status codes, exception handling (7.1-7.2) | Yes | Yes | Yes |
Note:
- For information about modifiers for Create Procedure and Create Function, see Unsupported modifiers and Unsupported optional modifiers.