[
https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570794#action_12570794
]
Kim Haase commented on DERBY-2653:
----------------------------------
Thanks, Kathey, I'll file an issue.
There is no need to hold off on the changes to the crefjavstateautogen topic.
That information will be important to have. The only change I was going to make
to that topic was to remove the specific reference to JDBC 3.0, because the
information applies to all versions of JDBC that we currently support. You
could do that yourself if you would like to.
If you wanted to fix the 3.0-specific Connection and Statement topics to
correct the information about column indexes and column names, that would be
okay too, since I haven't gotten to those and won't for a while. (I'm still
waiting for feedback on DERBY-3409 (fixes related to the JDBC 2.0 topics).
> Expose existing auto-generated key functionality through more JDBC APIs in
> Derby Client.
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-2653
> URL: https://issues.apache.org/jira/browse/DERBY-2653
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Environment: Runnning with Derby Client.
> Reporter: A B
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: crefjavstateautogen.html,
> derby-2653_columnIndexes_diff.txt, derby-2653_columnNames2_diff.txt,
> derby-2653_columnNames_diff.txt, derby-2653_columnNames_diff.txt,
> derby-2653_doc_diff.txt, derby-2653_proto_diff.txt
>
>
> See DERBY-2631 for details. Desired functionality is the same as for
> DERBY-2631, except that this issue is specifically for Derby Client
> (DERBY-2631 only addressed embedded mode).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
