RFR: 8369432: Add Support for JDBC 4.5 MR [v8]

[Alan Bateman]

On Fri, 17 Oct 2025 22:12:25 GMT, Lance Andersen <lancea at openjdk.org> wrote:

>> This PR adds support for the upcoming JDBC 4.5 MR which provides the following  updates to the JDBC specification:
>> 
>> - Deprecate SQLPermission for removal
>> - Enhance the Blob/Clob/Array/SQLXML/NClob interfaces to extend/support AutoClosable
>> - Add the SQL types DECFLOAT, JSON to Types.Java and JDBCType.java
>> - Add the quoted identifier methods that **were added previously to the Statement interface in JDK 9** to the Connection interface
>>   - It is the exact same verbiage & default methods used when these methods were added to the Statement interface
>> - Clarify the Timestamp::hashCode method which incorrectly indicates that nanos are not used when calculating the hash
>> 
>> Tiers 1-3 have been run
>
> Lance Andersen has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Minor wordsmithing based on approved CSR feedback

src/java.sql/share/classes/java/sql/Connection.java line 1726:

> 1724:      * <li>Return the original value if {@code alwaysDelimit} is
> 1725:      * {@code false}</li>
> 1726:      * <li>Return a delimited identifier if {@code alwaysDelimit} is

Is there somewhere that defines "delimited identifier" that this could link to? I think it means double quotes but at the same time it seems that this may not be supported by the JDBC driver or datasource. This makes me wonder if the default implementation should throw SQLFeatureNotSupportedException as I assume something is broken if this method is returning a quoted result that is not supported.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/27693#discussion_r2442895297