db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4015) Regression in Statement.getGeneratedKeys()
Date Wed, 14 Jan 2009 18:12:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-4015:

    Attachment: Derby4015.java

Attached is an updated program that separates the non-generated and fake column tests.   
Would someone who has access be willing to run this  on Postgress and/or MySQL?

Myrna suggested that I post the trunk plan too, based on my earlier proposal.  I think that
the following behavior would be the ultimate goal for both client and embedded:

emptyArray       : gen key RS
nonGen column: SQLE(X0XOF)
fakeColumn       : SQLE(XOXOF)
nullArray           : SQLE(X0XOF)
nullParam           : gen key RS

I am not sure how to implement the SQLExceptions for the nonGen and   fakeColumn cases for
client though.

> Regression in Statement.getGeneratedKeys()
> ------------------------------------------
>                 Key: DERBY-4015
>                 URL: https://issues.apache.org/jira/browse/DERBY-4015
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:
>         Environment: I am currently running on Mac 10.5 with Java 5. However, it has
also been observed on other platforms in our automated build such as SUSE Linux and Windows
with Java 5.
>            Reporter: Brandon Smith
>            Priority: Critical
>         Attachments: Behavior-Matrix.jpg, derby-, derby-,
Derby4015.java, Derby4015.java, updatedBehaviorMatrix.txt
> The application of both DERBY-2653 and DERBY-3426 in the seems to have created
a regression in how the network JDBC client implementation of PreparedStatement.getGeneratedKeys()
behaves as compared to Note that there wasn't a change in behavior between versions
for the embedded implementation. However, in general there are behavior discrepancies between
the network and client implementations for this method.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message