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
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - FluidShell - Command |
| Version | 12.0 |
\sqlexport invalid_table valid_table will end up with the data from valid_table printed on the screen and after that with the export failed message. This could suggest that getting all the data from the last table has failed.\cat inexistent_file valid_file, won't print an Exception message at the end.
Niels, please review this proposal and decide whether \sqlexport should handle error/exception the way as suggested. We can discuss it whenever you have time.
If all table/query succeed, then complete normally
If all table/query fail, then throw exception
If all 1 or more table/query succeed, and the rest fail then print to stderr "SQL Export has completed with errors" but do not throw exception.
If all table/query succeed, then complete normally
If all table/query fail, then throw exception
If all 1 or more table/query succeed, and the rest fail then print to stderr "SQL Export has completed with errors" but do not throw exception.
Done. SVN trunk/r30024.
Done. SVN trunk/r30024.
Verified using ADStudio 12.0.5, changes made as mentioned by Niels.
Closed.
Verified using ADStudio 12.0.5, changes made as mentioned by Niels.
Closed.
Issue #7881 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/30024 |
| No time estimate |
1 issue link |
relates to #7855
Issue #7855\sqlexport on erroneous SQL code from sqlbuffer: Exception or Error |
Niels, please review this proposal and decide whether \sqlexport should handle error/exception the way as suggested. We can discuss it whenever you have time.