Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Drop NativeJdbcExtractor mechanism in favor of JDBC 4 unwrap

Browse Source 
Issue: SPR-14670
This commit is contained in:
Juergen Hoeller
2017-02-15 18:04:08 +01:00
parent 54f01cffaf
commit 07dd61eabd
36 changed files with 124 additions and 1693 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
src/asciidoc/data-access.adoc
View File

@@ -3222,29 +3222,6 @@ pattern. JTA does not support custom isolation levels!
[[jdbc-NativeJdbcExtractor]]
==== NativeJdbcExtractor
Sometimes you need to access vendor specific JDBC methods that differ from the standard
JDBC API. This can be problematic if you are running in an application server or with a
`DataSource` that wraps the `Connection`, `Statement` and `ResultSet` objects with its
own wrapper objects. To gain access to the native objects you can configure your
`JdbcTemplate` with a `NativeJdbcExtractor`.
The `NativeJdbcExtractor` comes in a variety of flavors to match your execution
environment:
* SimpleNativeJdbcExtractor
* C3P0NativeJdbcExtractor
* JBossNativeJdbcExtractor
* WebLogicNativeJdbcExtractor
* WebSphereNativeJdbcExtractor
Usually the `SimpleNativeJdbcExtractor` is sufficient for unwrapping a `Connection`
object in most environments. See the javadocs for more details.
[[jdbc-advanced-jdbc]]
=== JDBC batch operations
Most JDBC drivers provide improved performance if you batch multiple calls to the same