db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5488) Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc.
Date Tue, 15 Nov 2011 15:10:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150543#comment-13150543
] 

Bryan Pendleton commented on DERBY-5488:
----------------------------------------

I am fine with the proposed implementation. I think I was getting somewhat confused between
compile-time support and run-time support.

My train-of-thought regarding my reaction was something like: if I am told that a particular

DB/driver/implementation is JDBC version X.Y, then I expect to look in the Javadocs for 
version X.Y and be able to call those APIs. 

I would not expect to have to use reflection to do so. 

When I look up, e.g., java.sql.PreparedStatement, I expect the "Since:" field to
help me with this comprehension. This doesn't work perfectly; for example, when I go to:
http://download.oracle.com/javase/6/docs/api/java/sql/PreparedStatement.html#setRowId(int,
java.sql.RowId)
I see that the setRowId() method is marked "Since: 1.6", and I have to know that this actually
means
"JDBC 4.0", but once I accomplish that, I know that I am calling a method that requires JDBC
4.0.

I note that when I go to http://www.oracle.com/technetwork/java/javase/jdbc/index.html which
is presumably the base of all the JDBC spec definitions, I am referred to JDBC documentation
for the base JDK, not by JDBC version number. That is, it says: 

        JDBC documentation: J2SE 1.4.2 | J2SE 5.0 | Java SE 6

At any rate, returning 4.1 seems fine to me; I think I am expressing a related, but independent,
confusion that affects the life of the JDBC application programmer :)

                
> Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc.
> -----------------------------------------------------------------------
>
>                 Key: DERBY-5488
>                 URL: https://issues.apache.org/jira/browse/DERBY-5488
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, SQL
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: JDBC_4.1_Supplement.html, derby-5488-01-aa-objectMappingAndConversion.diff,
derby-5488-02-aa-fixBigInteger.diff, derby-5488-03-ac-moveDecimalSetterGetterAndTest.diff,
derby-5488-04-aa-fixBigIntegerDecimal.diff, derby-5488-05-ad-limitOffset.diff, derby-5488-06-aa-limitOffsetTests.diff,
derby-5488-07-aa-booleanObjects.diff, derby-5488-08-aa-extraLimitOffsetTest.diff, derby-5488-09-aa-jdbcMinorVersion.diff,
z.java
>
>
> In addition to the JDBC 4.1 bits which were visible in the Java 7 javadoc, a couple other
items appear in the JDBC 4.1 Maintenance Review spec. This spec has been published on the
JCP website at http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-eval-spec/index.html.
I will attach a functional spec for the remaining bits.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message