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 | Q Analyzer - Grid Results |
| Version | Future |
Switching between MultiTab & SplitPane results will lose any existing result sets.
You should be able to switch back and forth and retain any existing result sets (pinned or not).
Note too, if you pin a result set and then switch modes the existing pinned sets disappear but if you execute a query the new result set from the execution will show up along with any previously pinned result sets.
|
|
24 KB
|
|
27 KB
Thanks for verifying the behavior I described. A user should be able to change between those two modes without loosing an executed query. Think about it from a user's perspective.. most users likely work in the Split Pane because they can see sql and results at the same time-- but once in a while you've just executed a large query, lots of results and want to see it in the full view. Expecting a user to re-execute the query is a bad user experience along with often painful as those larger data sets which make the most sense to go full page on often take longer to re-execute.
I'm not asking whether this is a bug or a feature or has existed since v7.0, I'm asking, from a user's perspective that this be changed. Please re-open.
Thanks for verifying the behavior I described. A user should be able to change between those two modes without loosing an executed query. Think about it from a user's perspective.. most users likely work in the Split Pane because they can see sql and results at the same time-- but once in a while you've just executed a large query, lots of results and want to see it in the full view. Expecting a user to re-execute the query is a bad user experience along with often painful as those larger data sets which make the most sense to go full page on often take longer to re-execute.
I'm not asking whether this is a bug or a feature or has existed since v7.0, I'm asking, from a user's perspective that this be changed. Please re-open.
Issue #13356 |
| Reopened |
Completion |
| No due date |
| No fixed build |
| No time estimate |