[ http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12420761 ]
David Van Couvering commented on DERBY-1395: -------------------------------------------- When the connection is closed, I think it's more informative on the client side, where it tells you that the connection is closed rather than just saying the statement is closed. I would argue that I should fix the embedded side to return 08003 when the connection is closed, that would actually be more consistent with the standard. However, in the case when the connection is open and the statement is closed, I will fix the client to use XJ012 instead of XCL31. > 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 > Type: Improvement > Components: Network Client > Versions: 10.2.0.0, 10.1.3.0 > Reporter: Deepa Remesh > Assignee: David Van Couvering > Priority: Trivial > > 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
