You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The one advantage of the psql-inspired UI concept was that once you submit the query, that query pops backwards into the history and clears the (smaller) editor area for continued editing.
The "equivalent" here would be opening a new tab each time you submit a query, which would be weird.
I kinda agree with @depombo that when the Run Query button is disabled the editor should also be disabled, so when the results come back you're 100% certain what the query was that produced the table you're looking at, because the user can open a new tab to start working on another query in the meantime if they want.
But that also might be annoying if you know you need to make just a small change to a large query for your next query, so I'm not sure about this.
We should probably prompt them to open a new tab
The text was updated successfully, but these errors were encountered: