Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException Error. Executing the same SQL using the \go command, FS prints a short Exception message go: Connection to RDBMS is already closed. The last Exception message should be shown in the first case as well.\connect my-server)\connect my-server -d different-db -k s2)\session command, everything looks OKselect 123 \ OR select 123 @ to get the first caseselect 123 <ENTER> \go to get the second case
Made change, SVN r30020, so that executing an inline SQL would generate the message below instead of an Exception with some stack trace:
Query not sent: server is disconnected.
The message above is the message that was implemented to report this sort of error in shell, I did not modify it.
Verified using ADStudio 12.0.5: "Query not sent: server is disconnected" Exception message is now printed for inline SQL executed on a Killed connection (except the first inline SQL executed, similar to the first \go cmd as mentinoned in the comments from #7820).
Closed.
Verified using ADStudio 12.0.5: "Query not sent: server is disconnected" Exception message is now printed for inline SQL executed on a Killed connection (except the first inline SQL executed, similar to the first \go cmd as mentinoned in the comments from #7820).
Closed.
Issue #7904 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #7820
Issue #7820Behavior in FluidShell after killing a connection |
Made change, SVN r30020, so that executing an inline SQL would generate the message below instead of an Exception with some stack trace:
Query not sent: server is disconnected.
The message above is the message that was implemented to report this sort of error in shell, I did not modify it.