You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/02/16 02:20:07 UTC
[jira] Updated: (DERBY-2653) Expose existing auto-generated key
functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-2653:
----------------------------------
Attachment: derby-2653_proto_diff.txt
Attached is a prototype of the change to forward the unimplemented methods to xxx(String sql, int autoGeneratedKeys). It is NOT for commit. The argument checking needs to be added, comments, and tests. I just thought the patch might ease discussion regarding the argument checking problem and make it clear that except for the argument checking these calls are the same as the existing autoGenerate keys methods.
> 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
> Priority: Minor
> Attachments: 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.