Open rwhirn opened 4 years ago
@huyphams I'm getting used to this and the workaround is to open a SQL Query window, select "all" and delete and then double click on the history query you want to work with and it will open it in the current (empty) window.
I hope you have time to get to this one as well.
Hi @rwhirn, we haven't supported opening the history query in a new SQL tab, just appending the query to current SQL statements. But we will consider it. Thank you for your feedback.
@son11592 @huyphams I'm sorry, but this makes no sense. If no SQL Query window is open at the time you double click on a history item, then you open one up with some random, totally unrelated query in it and then append this one after the last character of the old one, not even on a new line. So if you aren't paying attention, (which I wasn't the first half dozen times I did this), and/or if the random old query is long enough to take up the display area, you don't even see the history query you were trying to edit/rerun. It just looks like you got the totally wrong query pulled up.
I would not "consider" this an "enhancement", it is very clearly a bug.
@huyphams @son11592 I would like to bring this issue to your attention again. This bug blocks my productivity nearly every day. @son11592 said above that the program is "just appending the query to current SQL statements". That is not the case that I am complaining about. In my case I open a fresh instance of TablePlus and I want to work on a query I was executing some time ago. I find it in history and double click on it. It opens up a new tab with some other, random query in it and adds the query I want to work on to the end of it (and not even on a new line nor even a space in between the last word of the old query and the first word of the new query). This is not "just appending the query to current SQL statements", it is creating a random broken meaningless query. If I wanted to append this query from history to some other query I was working on (tho I can't think of any reason why I would ever want to do this), let me make the decision to append it by cutting and pasting, the program should not just assume I always want to append it and certainly not when I have no query open to begin with.
Please fix this bug!
Which driver are you using and version of it (Ex: PostgreSQL 10.0): MySQL 5.7.17
Which TablePlus build number are you using (the number on the welcome screen, Ex: build 81): 146
The steps to reproduce this issue: Double click on any previous query in History Instead of that query opening in its own query editor, it opens the previous query in SQL Query and appends this query to it Replaces issue #251