[
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_columnNames_diff.txt
Attached is a partial patch for this issue which implments the following API's
for client:
Connection.prepareStatement(String sql, String[] columnNames);
Statement.execute(String sql, String[] columNames);
Statement.executeUpdate(String sql, String[] columnNames);
The columnIndex calls have not yet been implemented. An argument of null for
columNames will return no generated keys. Otherwise client requires an array
of length 1 for columnNames. It will actually ignore the value and always
return the results of IDENTITY_VAL_LOCAL after the insert.
Users should only ever set columnNames to be the identity column.
Tests are running.
> 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_columnNames_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.
