Chat2DB Edition
Chat2DB Community
User Problem
SQL editor users need to inspect previous execution output and tabular results independently. The current interaction does not clearly separate Output log retention from result-tab retention, and retained results become difficult to identify, order, and close safely across repeated or multi-statement executions.
Concrete Use Case
Run several single- and multi-statement SQL submissions in one editor, keep the Output log for diagnosis, retain selected tabular results for comparison, switch between oldest-first and newest-first presentation, and close an individual result without late Desktop events recreating it. Disabling result retention should replace existing result tabs only on the next accepted execution without clearing Output.
Product Area
SQL editor
Proposed Outcome
Provide independent persisted controls for Output history and existing result tabs. Keep retained results in one flat tab strip with stable execution-batch identity, clear SQL summaries, table icons, uniform tab widths, and a fixed result-settings control. Ordering must preserve statement order inside each execution, and execution/cancellation handling must prevent overlapping requests, stale results, and duplicate close-shortcut handling.
Alternatives Considered
A single keep-history option couples logs and result data too tightly. A separate batch selector adds another navigation level and makes individual results slower to reach, so retained batches should remain flat and use batch identity only for ordering, replacement, and late-event barriers.
Contribution
I can submit a pull request
Submission Checklist
Chat2DB Edition
Chat2DB Community
User Problem
SQL editor users need to inspect previous execution output and tabular results independently. The current interaction does not clearly separate Output log retention from result-tab retention, and retained results become difficult to identify, order, and close safely across repeated or multi-statement executions.
Concrete Use Case
Run several single- and multi-statement SQL submissions in one editor, keep the Output log for diagnosis, retain selected tabular results for comparison, switch between oldest-first and newest-first presentation, and close an individual result without late Desktop events recreating it. Disabling result retention should replace existing result tabs only on the next accepted execution without clearing Output.
Product Area
SQL editor
Proposed Outcome
Provide independent persisted controls for Output history and existing result tabs. Keep retained results in one flat tab strip with stable execution-batch identity, clear SQL summaries, table icons, uniform tab widths, and a fixed result-settings control. Ordering must preserve statement order inside each execution, and execution/cancellation handling must prevent overlapping requests, stale results, and duplicate close-shortcut handling.
Alternatives Considered
A single keep-history option couples logs and result data too tightly. A separate batch selector adds another navigation level and makes individual results slower to reach, so retained batches should remain flat and use batch identity only for ordering, replacement, and late-event barriers.
Contribution
I can submit a pull request
Submission Checklist