[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12421746 ]
David Van Couvering commented on DERBY-1395:
Note: this passes the jdbc40 suite for both embedded and network clients.
Change the client SQLState to
[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12421766 ]
Knut Anders Hatlen commented on DERBY-1395:
---
Hi David,
I think the patch looks good. +1 to commit.
Change the client SQLState to match that of embedded
Knut Anders Hatlen (JIRA) derby-dev@db.apache.org writes:
[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12421766
]
Knut Anders Hatlen commented on DERBY-1395:
---
Hi David,
I think the patch looks good.
[
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
[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12417318 ]
Deepa Remesh commented on DERBY-1395:
-
I had seen the first scenario (both connection and statement closed) in
jdbcapi/checkDataSource.java.This is in the checkConnection
[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12417215 ]
David Van Couvering commented on DERBY-1395:
Deepa, is there a particular test that exemplifies this behavior? I could poke
around but if there are existing
[
http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12415827 ]
Knut Anders Hatlen commented on DERBY-1395:
---
The SQL states are different when the statement is closed and the connection
still open too:
Embedded: SQLSTATE =