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
If calling the Command mode FluidShell with the -ss (STOP_ON_SQL_ERROR) parameter set to false, or the command \source with -ss false, the "Script error on line X" message is not displayed.
Please note that the mentioned message is displayed if using the default value -ss true, and also for the case with the -sc (STOP_ON_CMD_ERROR) parameter set to either false or true.
Probably the SQL error is not seen as exception when -ss false is set and thus the "Script error on line: .." header is not written. Actually, this is a matter of consistency, because for the -sc parameter this header is displayed both if the parameter value is set to true or set to false.
The reason the SQL error is not seen on '-ss false' is because \go command did not throw that exception back to shell when -ss is set to false. I will discuss this with Niels to see whether \go command should always relay exception back to shell regardless the setting of -ss.
The reason the SQL error is not seen on '-ss false' is because \go command did not throw that exception back to shell when -ss is set to false. I will discuss this with Niels to see whether \go command should always relay exception back to shell regardless the setting of -ss.
Made change to throw exception back to shell from go command if \go is executed from a script so that the 'Script error on line X' message can be shown. As discussed in issue #7579, the SQL error message will not be displayed after 'Script error on line X'.
Made change to throw exception back to shell from go command if \go is executed from a script so that the 'Script error on line X' message can be shown. As discussed in issue #7579, the SQL error message will not be displayed after 'Script error on line X'.
Verified using ADStudio 12 Beta 38; 'Script error on line X' message is now displayed when using the -ss false parameter.
Closed.
Verified using ADStudio 12 Beta 38; 'Script error on line X' message is now displayed when using the -ss false parameter.
Closed.
Issue #7580 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/29284 |
| No time estimate |
1 issue link |
relates to #7579
Issue #7579Script error message for SQL errors via Command mode or \source |
Probably the SQL error is not seen as exception when -ss false is set and thus the "Script error on line: .." header is not written. Actually, this is a matter of consistency, because for the -sc parameter this header is displayed both if the parameter value is set to true or set to false.