[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487954
]
A B commented on DERBY-2538:
----------------------------
> is this just a question of what JDK I'm using?
Great question. Maybe JDK would in fact be clearer here. I went with "JDBC"
because the connection objects we are talking about implement (or don't) the
JDBC 4 interface methods. Use of "jdk 1.6" seemed slightly less appropriate to
me because it seems like it could theoretically be possible to have more than
one jdk that correlates to JDBC 4 (ex. jdk 1.4 and 1.5 both correlate to JDBC
3).
But I am notorious for messing up the JDK/JVM/JDBC terminology, so you're
probably right. I'll wait to see if anyone out there offers better wording.
> Did we invent the terminology "JDBC environment" or is this part of the JDBC
> specification?
Another good question. I just typed what came to me...maybe that's not a good
way of phrasing it. I did notice that in one of his comment Dan wrote:
"In a JDK 1.4/1.5 environment the applications must use the old ones (e.g.
EmbeddedConnectionPoolDataSource)"
So perhaps that's the wording that should go here...
> 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
> Priority: Minor
>
> 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.
