Run current query runs wrong query
Brought to you by:
ansgarbecker
Originally created by: andreas....@gmail.com
Version 3338
If you place the cursor directly after the statement delimiter, the
statement before the statement delimiter will be executed.
Example:
select * from a;<cursor> select * from b;
This will run statement a but the cursur is inside statement b.
I'm not sure what i will expect with linebreaks the following examples:
Example2:
select * from a;<cursor>
select * from b;
->cursor inside b
->runs a
Example3:
select * from a; <cursor>
select * from b;
->cursor inside b
->runs b
Example4:
select *
from a ;<cursor>
select *
from b;
->runs a
->cursor inside b
Example5:
select *
from a ; <cursor>
select *
from b;
->runs b
->cursor inside b
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
This issue was closed by revision [r3339].
Status: Fixed
Related
Commit: [r3339]
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: christop...@gmail.com
I think the update made in revision [r3339] to solve this issue has actually made it worse.
The different possibilities were well explained in the first comment but the solution
of running the query where the cursor is places makes the following kind of behavior :
Example:
select * from A;<cursor>
select * from B;
->runs B !!!!
This is a big problem since when you use Heidi, you type statement A then you add the
delimiter and finally you type ctrl+shift+F9 and guess what... the statement B is
executed instead of statment B !!! ??? !!!
I personnaly think that this new "Run Current Query" option is a mess and that there
will never be a satisfying solution to this kind of troubles.
The "Run current line" option was a lot safer.
I'm also opening a new issue since I consider this a very serious problem in Heidi.
Related
Commit: [r3339]