Bug #38943 | SQLException.getMessage() returns null, no indication of reason for error | ||
---|---|---|---|
Submitted: | 21 Aug 2008 16:13 | Modified: | 2 Jun 2015 20:14 |
Reporter: | Robert Simpson | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1.6 | OS: | Any (Win XP 5.1.2600) |
Assigned to: | Alexander Soklakov | CPU Architecture: | Any |
Tags: | getMessage, getstring, SqlException |
[21 Aug 2008 16:13]
Robert Simpson
[21 Aug 2008 20:04]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior with generic test case. Please provide example of code bug is repeatable with.
[22 Aug 2008 14:37]
Robert Simpson
See also forum message: http://forums.mysql.com/read.php?39,199533,200282#msg-200282 which says "getMessage() ... was null ... not very helpful"
[23 Aug 2008 10:48]
Sveta Smirnova
Thank you for the feedback. Verified as described.
[23 Aug 2008 10:49]
Sveta Smirnova
test case for the testsuite
Attachment: bug38943.java (text/plain), 647 bytes.
[2 Jun 2015 20:14]
Daniel So
Added the following entry to the Connector/J 5.1.7 changelog: "When an application using Connector/J ran into an error, the SQLException.getMessage() method was returning null instead of an error description. This has been fixed by calling the setRowPositionValidity() method in the ResultSetImpl constructor."