9.1 Scope of support for the result set extended functions
The following table shows HADB's scope of support for the result set extended functions (ResultSet class) of the JDBC 2.1 Core API.
|
Result set extended function (ResultSet class) |
HADB's scope of support |
|
|---|---|---|
|
Scrolling type |
Forward-only scrolling |
Y |
|
Scroll-insensitive scrolling |
Y |
|
|
Scroll-sensitive scrolling |
N |
|
|
Concurrent processing type |
Read-only processing |
Y |
|
Updatable |
N |
|
- Legend:
-
Y: Supported by HADB
N: Not supported by HADB
- Important
-
-
No error results if an unsupported scrolling type or concurrent processing type is specified. The JDBC 2.1 Core API assumes the result set that is closest to the specified scrolling type or concurrent processing type, and creates an instance of the Statement class or that subclass. In this case, the API generates a warning (SQLWarning object) and associates it with an instance of the Connection class.
-
In the case of a scrolling-type result set, all retrieved data is cached in the JDBC driver. This means that a large amount of data increases the possibility of a memory shortage or deterioration in performance. When you use a scrolling-type result set, take steps in advance to minimize the volume of retrieved data by, for example, adding appropriate conditions to the SQL statements.
-