Skip to content

'Execute Current Line' does not work as expected in Windows - executes current and next statements #1768

Closed

Description

@kharaktur

Details for the issue

What did you do?

What did you expect to see?

What did you see instead?

Useful extra information

DB4S v3.11.1 [built for i386-little_endian-ilp32] on Windows 7 SP 1 (winnt/6.1.7601) [x86_64]
using SQLite Version 3.27.1
and Qt 5.7.1

Activity

  1. kharaktur commented on Feb 25, 2019

    @kharaktur
    Author

    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.

  2. 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
  3. chrisjlocke commented on Feb 25, 2019

    @chrisjlocke
    Member

    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.

  4. kharaktur commented on Feb 25, 2019

    @kharaktur
    Author
  5. added
    bugConfirmed bugs or reports that are very likely to be bugs.
    on Feb 25, 2019
  6. self-assigned this
    on Jan 4, 2020
  7. 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
  8. mgrojo commented on Jan 4, 2020

    @mgrojo
    Member

    @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?

  9. added this to the 3.12.0 - Next release milestone on Jan 4, 2020
  10. kharaktur commented on Jan 8, 2020

    @kharaktur
    Author
  11. mgrojo commented on Jan 8, 2020

    @mgrojo
    Member

    Great! Thanks for confirming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugConfirmed bugs or reports that are very likely to be bugs.windows

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions