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 | Minor |
| Complexity | Unknown |
| Component | App - FluidShell - SQL Buffer |
| Version | Future - PM |
a) what happens currently is that my sqlbuffer is cleared & the sql stmt is placed into sqlhistory
b) another option is that since an error occurred, the stmt stays in my current sqlbuffer. This way, I can type edit to fix my error & execute again.
I still don't agree with this. "error occured" is vague since so many things can happen. "error occured" could be 1) connection is closed 2) application throws exception 3) Database server throws exception 4) Database server throws warning.
The current behavior is the way all other shells work.
Issue #6780 |
| New |
Completion |
| No due date |
| No fixed build |
| No time estimate |
I still don't agree with this. "error occured" is vague since so many things can happen. "error occured" could be 1) connection is closed 2) application throws exception 3) Database server throws exception 4) Database server throws warning.
The current behavior is the way all other shells work.