[ http://issues.apache.org/jira/browse/DERBY-1395?page=all ]
David Van Couvering resolved DERBY-1395.
----------------------------------------
Resolution: Fixed
Passes jdbc40 and derbyall test suites
Sending java/client/org/apache/derby/client/am/Statement.java
Sending java/engine/org/apache/derby/impl/jdbc/EmbedStatement.java
Sending
java/testing/org/apache/derbyTesting/functionTests/master/checkDataSource.out
Sending
java/testing/org/apache/derbyTesting/functionTests/master/checkDataSource30.out
Sending
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/ClosedObjectTest.java
Transmitting file data .....
Committed revision 423141.
> Change the client SQLState to match that of embedded for the exception thrown
> on a closed statement whose connection is also closed
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1395
> URL: http://issues.apache.org/jira/browse/DERBY-1395
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Affects Versions: 10.2.0.0, 10.1.3.0
> Reporter: Deepa Remesh
> Assigned To: David Van Couvering
> Priority: Trivial
> Attachments: DERBY-1395.diff
>
>
> Scenario: Both connection and statement are closed and an operation is
> performed on a closed statement. SQLStates are as follows:
> Embedded: SQLSTATE: XJ012, Message: Statement Closed
> Client before DERBY-843 fix: SQLSTATE = null, message = Statement closed
> Client after DERBY-843 fix: SQLSTATE: 08003, Message: connection closed
> This issue is related to the effort started in DERBY-254.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
