[
https://issues.apache.org/jira/browse/DERBY-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Smith updated DERBY-4015:
---------------------------------
Attachment: Behavior-Matrix.jpg
Consider the attached screenshot illustrating a behavior matrix between client
and embedded, versions 10.3.2.1 and 10.3.3.0, and four test cases.
The test cases each call Connection.prepareStatement(String, String[]) with
different values.
emptyArray == new String[] { }
fakeColumn == new String[] { "value" } where value is not a column
nullArray == new String[] { null }
nullParam == null
The matrix then records how each behaves and illustrates how the behavior
changes not only across versions, but also between client and embedded
implementations.
> 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: 10.3.3.0
> 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
>
>
> The application of both DERBY-2653 and DERBY-3426 in the 10.3.3.0 seems to
> have created a regression in how the network JDBC client implementation of
> PreparedStatement.getGeneratedKeys() behaves as compared to 10.3.2.1. 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.
