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 |
Currently, if one calls the sqlexport command without a table specified, so that the query from the sqlbuffer is executed, the sqlbuffer remains unmodified.
In other situations when the query from the sqlbuffer is called for execution, after the execution the sqlbuffer is cleared.
This question came up after looking at Issue #6580 - \source command not allowing me to use \clear sql command --- where one of the comments mentions this.
---
Related Issue #6780 - When I execute a sql statement in FluidShell & an error is returned what should happen to the sqlbuffer?
Another issue in which the clearing of the sqlbuffer is discussed: #6555 - \source side-effect on the SQL query buffer.
Not sure what we discussed originally. I do think we should clear the sqlbuffer after an sqlexport.
Not sure what we discussed originally. I do think we should clear the sqlbuffer after an sqlexport.
sqlexport will attempt to execute buffered statements if
(1) there is a connection,
(2) all of command line validations have passed,
(3) no tables specified.
Once an execution attempt of buffered statements is made, sqlexport will:
(1) add buffered statements to sqlhistory before the execution attempt,
(2) clear the sqlbuffer after the execution attempt, regardless the status of the execution.
sqlexport will attempt to execute buffered statements if
(1) there is a connection,
(2) all of command line validations have passed,
(3) no tables specified.
Once an execution attempt of buffered statements is made, sqlexport will:
(1) add buffered statements to sqlhistory before the execution attempt,
(2) clear the sqlbuffer after the execution attempt, regardless the status of the execution.
Verified using ADStudio 12 Dev 126, the sqlbuffer gets cleared now.
A bug was found when checking for the second case with an invalid statement, posted as #7285 - Exception printed in Command mode for \sqlexport if invalid sql statement.
Current issue Closed.
Verified using ADStudio 12 Dev 126, the sqlbuffer gets cleared now.
A bug was found when checking for the second case with an invalid statement, posted as #7285 - Exception printed in Command mode for \sqlexport if invalid sql statement.
Current issue Closed.
Issue #7175 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/28127 |
| No time estimate |
Another issue in which the clearing of the sqlbuffer is discussed: #6555 - \source side-effect on the SQL query buffer.