7.1.1 Scope of JDBC standards compliance
HADB is implemented with the Type 4 JDBC driver. The following table shows the scope of the JDBC standards with which the HADB JDBC driver is compliant.
|
No. |
JDBC standard |
Function |
Compliant |
|---|---|---|---|
|
1 |
The JDBCTM API, Version 1.20 (JDBC 1.2 API) |
Driver interface |
Y |
|
2 |
Connection interface |
Y |
|
|
3 |
Statement interface |
Y |
|
|
4 |
PreparedStatement interface |
Y |
|
|
5 |
CallableStatement interface |
N |
|
|
6 |
ResultSet interface |
Y |
|
|
7 |
DatabaseMetaData interface |
Y |
|
|
8 |
ResultSetMetaData interface |
Y |
|
|
9 |
Blob interface |
N |
|
|
10 |
Array interface |
N |
|
|
11 |
SQLException interface |
Y |
|
|
12 |
SQLWarning interface |
Y |
|
|
13 |
The JDBCTM 2.1 API, Version 1.1 (the JDBC 2.1 Core API) |
Result set extensions |
L#1 |
|
14 |
Batch updating |
Y |
|
|
15 |
Support for persistent Java objects |
N |
|
|
16 |
Addition of JDBC SQL data types |
N |
|
|
17 |
Custom mapping of data types |
N |
|
|
18 |
The JDBC 2.0 Standard Extension API, Version 1.0 (the JDBC 2.0 Optional Package API) |
JNDI |
Y |
|
19 |
Connection pool |
Y |
|
|
20 |
Distributed transactions (JTA support) |
N |
|
|
21 |
Row sets |
N |
|
|
22 |
JDBCTM 3.0 Specification (JDBC 3.0 API) |
Save points |
N |
|
23 |
Enhancement of the connection pool function |
N |
|
|
24 |
Parameter metadata |
Y |
|
|
25 |
Automatic generation keys |
N |
|
|
26 |
Concurrent opening of multiple result sets |
N |
|
|
27 |
Use of parameter names in CallableStatement |
N |
|
|
28 |
Holdable cursors |
Y |
|
|
29 |
BOOLEAN type |
N |
|
|
30 |
Data manipulation in the Blob class |
N |
|
|
31 |
Reference type |
N |
|
|
32 |
DATALINK and URL types |
N |
|
|
33 |
JCA-related architectures |
N |
|
|
34 |
API for adding database metadata |
Y |
|
|
35 |
JDBCTM 4.0 Specification (JDBC 4.0 API) |
Automatic loading of java.sql.Driver |
Y |
|
36 |
ROWID data type |
N |
|
|
37 |
National character data type |
N |
|
|
38 |
Enhancement of BLOB and CLOB functions |
N |
|
|
39 |
XML support |
N |
|
|
40 |
Wrapper pattern |
Y |
|
|
41 |
SQL exception extensions |
Y |
|
|
42 |
Connection management |
L#2 |
|
|
43 |
Addition of scalar functions |
L#3 |
|
|
44 |
API for adding database metadata |
Y |
|
|
45 |
JDBCTM 4.1 Specification (JDBC 4.1 API) |
try-with-resources statement |
Y |
|
46 |
Java data type of conversion target of getObject method |
L#4 |
|
|
47 |
Acquisition of parent logger |
N |
|
|
48 |
Schema specification |
N |
|
|
49 |
Closing and timing out physical connections |
N |
|
|
50 |
Closing Statement objects when dependent objects are closed |
Y |
|
|
51 |
API that adds database metadata |
Y |
|
|
52 |
JDBCTM 4.2 Specification (JDBC 4.2 API) |
REF CURSOR |
N |
|
53 |
SQLType interface |
N |
|
|
54 |
JDBCType enumerator (Enum) |
N |
|
|
55 |
Large update counts |
Y |
|
|
56 |
API that adds database metadata |
Y |
- Legend:
-
Y: Supported
L: Limited support
N: Not supported
- #1
-
Only the scroll function is supported.
- #2
-
Only Connection#isValid() and Statement#isPoolable() are supported.
- #3
-
Only CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, and EXTRACT are supported.
- #4
-
A getObject method of the ResultSet interface. This method only supports conversion to some Java data types. For details, see 8.5.43 getObject(int columnIndex,Class<T> type).
Hereafter, the term JDBC driver refers to the Type 4 JDBC driver.