[
https://issues.apache.org/jira/browse/DERBY-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486656
]
Dag H. Wanvik commented on DERBY-2511:
--------------------------------------
Kim>
Kim> [
https://issues.apache.org/jira/browse/DERBY-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486402
]
Kim>
Kim> Kim Haase commented on DERBY-2511:
Kim> ----------------------------------
Kim>
Kim> Thanks, that's pretty clear. Is there anything else to be said
Kim> about what those JDBC 4.0-specific interfaces are for? Do people
Kim> still need to use them if they want to run on JDK 6?
The
EmbeddedConnectionPoolDataSource40 and
EmbeddedDataSource40
EmbeddedXADataSource40
ClientConnectionPoolDataSource40 and
ClientDataSource40
ClientXADataSource40
makes available the Wrapper functionality (isWrapperFor, unwrap
methods) described earlier in this section ("JDBC 4.0-only features",
feature bullet "Wrappers"). I think they are only needed if the
application expects to be able to use this functionaliy for
portability reasons (they expose no vendor-specific extensions for
Derby).
Anything more to be said on this, Rick?
Btw, why are EmbeddedDriver and ClientDriver referred to as DataSource
in this section ("javax.sql.DataSource interface: JDBC 4.0 features")?
Thanks,
Dag
Kim>
Kim> > reference manual's description of JDBC4 features has misleading sections
Kim> > ------------------------------------------------------------------------
Kim> >
Kim> > Key: DERBY-2511
Kim> > URL: https://issues.apache.org/jira/browse/DERBY-2511
Kim> > Project: Derby
Kim> > Issue Type: Bug
Kim> > Components: Documentation
Kim> > Affects Versions: 10.2.1.6, 10.2.2.0
Kim> > Reporter: Dag H. Wanvik
Kim> > Priority: Trivial
Kim> >
Kim> > The following sentences under section "javax.sql.DataSource interface:
JDBC 4.0 features" should be removed since the feature described is not part of
JDBC4 (EoD was withdrawn prior to final release):
Kim> > "JDBC 4.0 introduces a simpler mechanism for iterating through a table.
You use this mechanism by passing an annotated query to your DataSource's
createQueryObject method. To expose this createQueryObject method,"
Kim> > Also, the section "java.sql.Connection interface: JDBC 4.0 features"
contains these sentences which should be removed:
Kim> > "Ease of development - JDBC 4.0 introduces DataSet, a simple mechanism
to iterate through a table. You obtain a DataSet by passing an annotated query
to your Connection's createQueryObject method."
Kim> > See ref/rrefjdbc4_0dataSource.dita, ca line 34 and
ref/rrefjdbc4_0connection.dita ca line 42.
Kim>
Kim> --
Kim> This message is automatically generated by JIRA.
Kim> -
Kim> You can reply to this email to add a comment to the issue online.
Kim>
> reference manual's description of JDBC4 features has misleading sections
> ------------------------------------------------------------------------
>
> Key: DERBY-2511
> URL: https://issues.apache.org/jira/browse/DERBY-2511
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.6, 10.2.2.0
> Reporter: Dag H. Wanvik
> Assigned To: Kim Haase
> Priority: Trivial
> Attachments: DERBY-2511.diff, rrefjdbc4_0connection.html,
> rrefjdbc4_0dataSource.html
>
>
> The following sentences under section "javax.sql.DataSource interface: JDBC
> 4.0 features" should be removed since the feature described is not part of
> JDBC4 (EoD was withdrawn prior to final release):
> "JDBC 4.0 introduces a simpler mechanism for iterating through a table. You
> use this mechanism by passing an annotated query to your DataSource's
> createQueryObject method. To expose this createQueryObject method,"
> Also, the section "java.sql.Connection interface: JDBC 4.0 features" contains
> these sentences which should be removed:
> "Ease of development - JDBC 4.0 introduces DataSet, a simple mechanism to
> iterate through a table. You obtain a DataSet by passing an annotated query
> to your Connection's createQueryObject method."
> See ref/rrefjdbc4_0dataSource.dita, ca line 34 and
> ref/rrefjdbc4_0connection.dita ca line 42.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
