The following functions should be implemented (should not raise SQLFeatureNotSupportedException when called with supported resultSetHoldability value, referenced as holdability below):
createStatement(type, concurrency, holdability)prepareCall(sql, type, concurrency, holdability)prepareStatement(sql, type, concurrency, holdability)
Also the following methods should be supported:
getHoldability()setHoldability(holdability)
The DatabaseMetaData.supportsResultSetHoldability(holdability) should return appropriate values for both ResultSet.HOLD_CURSORS_OVER_COMMIT and ResultSet.CLOSE_CURSORS_AT_COMMIT. The DatabaseMetaData.getResultSetHoldability() should return a default holdability: one of two values above.
The issue is about proper APIs support, so it seems that one of the holdability values support is enough. It depends of Tarantool/SQL cursors implementation or, maybe, cursors emulation support of the driver.
The following functions should be implemented (should not raise
SQLFeatureNotSupportedExceptionwhen called with supported resultSetHoldability value, referenced asholdabilitybelow):createStatement(type, concurrency, holdability)prepareCall(sql, type, concurrency, holdability)prepareStatement(sql, type, concurrency, holdability)Also the following methods should be supported:
getHoldability()setHoldability(holdability)The
DatabaseMetaData.supportsResultSetHoldability(holdability)should return appropriate values for bothResultSet.HOLD_CURSORS_OVER_COMMITandResultSet.CLOSE_CURSORS_AT_COMMIT. TheDatabaseMetaData.getResultSetHoldability()should return a default holdability: one of two values above.The issue is about proper APIs support, so it seems that one of the holdability values support is enough. It depends of Tarantool/SQL cursors implementation or, maybe, cursors emulation support of the driver.