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
'Execute Current Line' does not work as expected in Windows - executes current and next statements #1768
Execute SQL tab. When multiple statements are present executing the current line (with Ctrl+F5 or the icon) results in all statements running sequentially. All statements are on separate lines and terminated with ; Seems to only be a problem with this version built for windows.
changed the title [-]Version 3.11.1 Built for i386-little_endian-ilp32, running on x86_64[/-][+]'Execute Current Line' does not work as expected - executes all statements[/+]on Feb 25, 2019
I believe this has been reported before in the nightlies, but is still a bit broken.
As a workaround, you can highlight the SQL statement you want to run, and click the F5 button. Pressing F5 only runs the highlighted SQL statements. Its more effort, but should be easier than commenting out chunks of SQL statements.
So three statements. Seems that clicking in a line executes the next one. My first attempt was to just click play, and as expected, the last statement is the only one visible, so it ran all three statements.
Not sure why at 0:15, the result column for 'c' is smaller than the one at 0:12. Running just one statement gives a smaller column. Never mind..... scratches head
0:20 onwards just shows highlighting works as desired.
changed the title [-]'Execute Current Line' does not work as expected - executes all statements[/-][+]'Execute Current Line' does not work as expected in Windows - executes current and next statements[/+]on Jan 4, 2020
@kharaktur I think I have fixed this issue. It took a lot of time because we weren't aware of it, since it only happens under Windows. Can you confirm it works well for you using tomorrow's nightly build?
Works correctly now, thanks.
--
Sent from my Android phone with GMX Mail. Please excuse my brevity.On 01/04/2020, 1:49 PM Manuel <notifications@github.com> wrote:
@kharaktur I think I have fixed this issue. It took a lot of time because we weren't aware of it, since it only happens under Windows. Can you confirm it works well for you using tomorrow's nightly build?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
Activity
kharaktur commentedon Feb 25, 2019
Execute SQL tab. When multiple statements are present executing the current line (with Ctrl+F5 or the icon) results in all statements running sequentially. All statements are on separate lines and terminated with ; Seems to only be a problem with this version built for windows.
[-]Version 3.11.1 Built for i386-little_endian-ilp32, running on x86_64[/-][+]'Execute Current Line' does not work as expected - executes all statements[/+]chrisjlocke commentedon Feb 25, 2019
I believe this has been reported before in the nightlies, but is still a bit broken.
As a workaround, you can highlight the SQL statement you want to run, and click the F5 button. Pressing F5 only runs the highlighted SQL statements. Its more effort, but should be easier than commenting out chunks of SQL statements.
Here is a screencast of my experiment.
https://screencast-o-matic.com/watch/cqnTbd06kM
So three statements. Seems that clicking in a line executes the next one. My first attempt was to just click play, and as expected, the last statement is the only one visible, so it ran all three statements.
Not sure why at 0:15, the result column for 'c' is smaller than the one at 0:12. Running just one statement gives a smaller column. Never mind..... scratches head
0:20 onwards just shows highlighting works as desired.
kharaktur commentedon Feb 25, 2019
[-]'Execute Current Line' does not work as expected - executes all statements[/-][+]'Execute Current Line' does not work as expected in Windows - executes current and next statements[/+]Take into account Windows line separator in Execute SQL
mgrojo commentedon Jan 4, 2020
@kharaktur I think I have fixed this issue. It took a lot of time because we weren't aware of it, since it only happens under Windows. Can you confirm it works well for you using tomorrow's nightly build?
kharaktur commentedon Jan 8, 2020
mgrojo commentedon Jan 8, 2020
Great! Thanks for confirming.