db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Date Wed, 11 Apr 2007 22:22:32 GMT

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

A B commented on DERBY-2538:
----------------------------

Thank you for picking this up, Kim, and for posting the changes so quickly.

I've read over the changes as you have them and they look good.  I have to admit, though,
that something about the phrase "use the JDBC 4 API" has me hesitating...

In a way I guess I'm just applying Bryan's earlier question to this particular phrase, namely:

How do I know if my application "uses the JDBC 4 API"?  Does this mean that the application
explicitly calls methods which are only available in the JDBC 4 API?  If so, then does that
mean that an application which runs on the Java SE 6 platform but which does not use any JDBC4-specific
APIs is *not* "using the JDBC 4 API"?  Technically I think such an application still has the
option of using either DataSource variant...

In some ways I wonder if it would be clearer to just focus on the jdk/platform.  I.e.:

----

Applications that run on the J2SE 1.4 or 1.5 platform must use the first variant. Applications
that run on the Java SE 6 platform can use either of the two variants. However, the DataSource
methods specific to the JDBC 4 API are available only from the second variant (the one whose
class name ends with "40").

If an application is running on the Java SE 6 platform, all connection objects returned from
the DataSource will be JDBC 4 connection objects, regardless of which DataSource variant is
in use.

----

This then goes back to Bryan's other question: is this [really] just a question of what JDK
I'm using? If so, then would the above snippet be good enough?

On a different note, I glanced at the "Network Server and Administration Guide" and I noticed
there are two pages about DataSources there, as well.  Once we figure out what it is we want
to say, these two pages should probably be updated accordingly:

  http://db.apache.org/derby/docs/dev/adminguide/cadminnsdatasources.html
  http://db.apache.org/derby/docs/dev/adminguide/cadminappsxawthdriver.html

In fact, I think it might be good to change the first of these so that it more closely matches
the content of http://db.apache.org/derby/docs/dev/devguide/rdevresman79556.html, with the
appropriate datasource name changes...

> Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC
3 datasource.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2538
>                 URL: https://issues.apache.org/jira/browse/DERBY-2538
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.2.2.0, 10.3.0.0
>            Reporter: A B
>         Assigned To: Kim Haase
>            Priority: Minor
>         Attachments: cdevresman89722.html, DERBY-2538.diff, rdevresman79556.html
>
>
> Based on discussion from DERBY-2488, pages in the Developer's Guide should be improved
to describe what happens if a JDBC 4 application uses an "old" (JDBC 3) datasource.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message