Raise JDBC driver feature baseline to JDBC 4.0+ [SPR-13826]

[spring-projects-issues]

Juergen Hoeller opened SPR-13826 and commented

Let's drop outdated adaptation code in StatementCreatorUtils and related classes, assuming a JDBC 4.1 driver (JDK 7 level) which implies full support for all mandatory JDBC 4.0 features (including ParameterMetaData.getParameterType).

After all, at this point, we're even defensive against JDBC 4.0 features which were introduced back in 2006... Spring 5 will still leniently handle exceptions with fallback code paths but won't try to detect and cache non-compliant drivers anymore.

---

Issue Links:

• "Parameter metadata not available for the given statement" SQL Exception after upgrading to Spring 5.0 RC4 [SPR-15977] #20528 "Parameter metadata not available for the given statement" SQL Exception after upgrading to Spring 5.0 RC4
• Doc: ParameterMetaData.getParameterType performance on Oracle 12c [SPR-16139] #20687 Doc: ParameterMetaData.getParameterType performance on Oracle 12c
• Protect against getParameterType cursor leak with Oracle 12c JDBC driver [SPR-14629] #19196 Protect against getParameterType cursor leak with Oracle 12c JDBC driver

Referenced from: commits 5ac7a32