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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2008/02/16 22:29:08 UTC

[jira] Issue Comment Edited: (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:comment-tabpanel&focusedCommentId=12569612#action_12569612 ] 

djd edited comment on DERBY-2653 at 2/16/08 1:27 PM:
-----------------------------------------------------------------------

One approach might be to only accept one column arrays and then document something like:

   The  one element column name or position array is ignored currently and the value returned corresponds to the identity column. To ensure compatibility with future changes an application should ensure the column described is the identity column. If the column name or position corresponds to another column  or a non-existent column then future changes may result in a value for a different column being returned or an exception being thrown.

[edit - add possibility for an error in the future]

      was (Author: djd):
    One approach might be to only accept one column arrays and then document something like:

   The  one element column name or position array is ignored currently and the value returned corresponds to the identity column. To ensure compatibility with future changes an application should ensure the column described is the identity column. If the column name or position corresponds to another column then future changes may result in a value for a different column being returned.
  
> 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.