db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
Date Wed, 20 Feb 2008 16:55:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570746#action_12570746
] 

Kim Haase commented on DERBY-2653:
----------------------------------

I've been following this issue to check on the possible impact on our JDBC documentation.


If I've understood correctly (not a sure thing), the restriction that "the user must specify
an array of columnIndexes of length 1" would be a new one. Currently in http://db.apache.org/derby/docs/dev/ref/rrefjdbcjavasqlconnection30.html
and http://db.apache.org/derby/docs/dev/ref/rrefjdbcjavasqlstatement30.html we
say, for Connection.prepareStatement, Statement.execute, and Statement.executeUpdate,

"Every column index in the array must correlate to an auto-increment column within the target
table of the INSERT."

(And similarly for the methods that take a columnNames argument.) These statements imply that
the array can have more than one element, so people might have to change existing code. The
change in the documentation would be no problem, but the change in behavior (if real) might
be a concern. What have I misunderstood?

I think a table can have more than one autoincrement column, although that might be an unusual
practice -- I don't see any restriction on this in the generated-column-spec topic (http://db.apache.org/derby/docs/dev/ref/rrefsqlj37836.html).


I think the rrefjdbcjavasqlconnection30 and rrefjdbcjavasqlstatement30 topics would need to
be changed along with crefjavstateautogen, although if I do all the work described in my DERBY-2388
proposal, the information in them would be folded into other 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.


Mime
View raw message