[DERBY-6484] Include SQLState in client exception messages

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Network Client
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 19/Feb/14 12:21
• Updated: 21/Jan/15 00:23
• Resolved: 25/Feb/14 08:48

Description

When the embedded driver raises an SQLException, it is linked to a iapi.error.StandardException whose toString() method adds the SQLState to the error message. An SQLException raised by the client driver is linked to a client.am.SqlException, which does not add the SQLState. Because of this, printStackTrace() gives more information when called on an embedded exception. You have to call getSQLState() on the client exception in order to see the SQLState.

We should change client.am.SqlException's toString() method to work the same way as StandardException.toString().

See also the discussion in DERBY-1997.

Issue Links

• is related to: DERBY-6488 Get rid of the EmbedSQLException class
• relates to: DERBY-1997 Misleading text in WwdEmbedded demo source file for Working With Derby