[
https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570781#action_12570781
]
Kim Haase commented on DERBY-2653:
----------------------------------
Oh, I see. No problem, then, as far as behavior goes.
But I looked all over, and I don't think we actually say that explicitly
anywhere -- not in the Reference Manual, anyway. I see an error message to that
effect, but that's all. Should that information be added to the
generated-column-spec topic
(http://db.apache.org/derby/docs/dev/ref/rrefsqlj37836.html)? If so, I can file
and fix a JIRA issue.
> 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.
