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
{{ message }}
Repository navigation
Shift+F5 shortcut does not work in Execute SQL tab #1491
Do you mean Shift+F5 (as you say in the title) or just F5 (as you say in the text)? 😄 Shift+F5 is sensitive to the current line. So if the cursor is for example in an empty line nothing will happen.
I've just reproduced this, but not sure how. It's working in the English version, but in the Spanish translation it doesn't work currently. The same is happening to "Shift+F1" which should enter in "What's this" mode. In the Help menu the shortcut is not displayed, but I'm sure to have seen it while I was updating the translation, as May+F1 (Spanish for Shift+F1).
@Bluezy Are you using a translated version? Could you change provisionally to English just to see if it works again?
I fixed the Spanish translation and now both Shift+F1 and Shift+F5 worked again. They weren't working since I updated the translation. If it weren't by this (possibly unrelated) issue, I wouldn't have notice in a while 😄
@Bluezy If you were using a translation it might be related. Then we could fix that translation so it works Ok.
Yep. You nailed it!
As soon as I add the final semicolons ; my shortcuts (e.g. F5) work again.
All in all, I am not sure whether this behaviour is a bug or a feature but thanks a lot for your suggestions though.
In the long past I am pretty sure I was not forced to add any semicolon in the Editor SQL but again, from now on, I will keep this in mind... :-)
Activity
MKleusberg commentedon Aug 5, 2018
Do you mean Shift+F5 (as you say in the title) or just F5 (as you say in the text)? 😄 Shift+F5 is sensitive to the current line. So if the cursor is for example in an empty line nothing will happen.
mgrojo commentedon Aug 6, 2018
I've just reproduced this, but not sure how. It's working in the English version, but in the Spanish translation it doesn't work currently. The same is happening to "Shift+F1" which should enter in "What's this" mode. In the Help menu the shortcut is not displayed, but I'm sure to have seen it while I was updating the translation, as May+F1 (Spanish for Shift+F1).
@Bluezy Are you using a translated version? Could you change provisionally to English just to see if it works again?
Use official Qt translation for Shift key
mgrojo commentedon Aug 6, 2018
I fixed the Spanish translation and now both Shift+F1 and Shift+F5 worked again. They weren't working since I updated the translation. If it weren't by this (possibly unrelated) issue, I wouldn't have notice in a while 😄
@Bluezy If you were using a translation it might be related. Then we could fix that translation so it works Ok.
justinclift commentedon Aug 6, 2018
Heh Heh Heh. Learn something interesting almost every day. 😁
chrisjlocke commentedon Aug 16, 2018
@Bluezy - Can you try one of our nightlies, which can be found here:
https://nightlies.sqlitebrowser.org/latest
justinclift commentedon Sep 7, 2018
Closing this due to lack of response.
SilvioGrosso commentedon Nov 15, 2018
I encountered this same bug.
Windows 10 (64 bit) - Nightly builds (12 November)
I have downloaded: DB.Browser.for.SQLite-win64.exe
Whenever you select the line with your SQL code an error always pops up.
At present, it only works when you select the last group of lines of code
Here is screenshot (the third SQL code works when I select it but not the previous two):

mgrojo commentedon Nov 15, 2018
Could it be #1575 (comment) (last Martin's answer). You don't use semicolons, so I guess it is related. What happens if you add semicolons?
SilvioGrosso commentedon Nov 15, 2018
Hello @mgrojo
Yep. You nailed it!
As soon as I add the final semicolons ; my shortcuts (e.g. F5) work again.
All in all, I am not sure whether this behaviour is a bug or a feature but thanks a lot for your suggestions though.
In the long past I am pretty sure I was not forced to add any semicolon in the Editor SQL but again, from now on, I will keep this in mind... :-)