Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.1.29
-
None
-
CentOS7
Description
When something goes wrong with the execution of a CONNECT JDBC statement (typically a SELECT) the error message doesn't contain enough information. A typical error message would be as follows:
Got error 174 'Cannot get result size rc=-1' from CONNECT)
|
The remote database is likely returning a detailed error message, and this should be passed along into the connect error message... maybe something like:
Got error 174 'Cannot get result size rc=-1 (Table Custumers does not exist)' from CONNECT)
|
i.e. just nest the message. This is hopefully very easy by calling exception.getLocalizedMessage() on any exception thrown from JDBC and passing the returned text along in error messages.