-
ClassDescriptionas of 5.3, in favor of Spring's common bean definition formats and/or custom reader implementations
-
MethodDescriptionas of 5.3, in favor of
JdbcOperations.query(String, ResultSetExtractor, Object...)
as of 5.3, in favor ofJdbcOperations.query(String, RowCallbackHandler, Object...)
as of 5.3, in favor ofJdbcOperations.query(String, RowMapper, Object...)
as of 5.3, in favor ofJdbcOperations.queryForList(String, Class, Object...)
as of 5.3, in favor ofJdbcOperations.queryForObject(String, Class, Object...)
as of 5.3, in favor ofJdbcOperations.queryForObject(String, RowMapper, Object...)
as of 5.1.11, in favor ofDataSourceUtils.resetConnectionAfterTransaction(Connection, Integer, boolean)
as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of 5.3, in favor of the JDBC 4.0 connection validationas of 5.2.9, in favor ofJdbcUtils.extractDatabaseMetaData(DataSource, DatabaseMetaDataCallback)
with a lambda expression or method reference and a generically typed result