[11.0.35 Pro] - Select Current Statement incremental bug

[11.0.35 Pro] - Select Current Statement incremental bug

The Select Current Statement feature has a nice little enhancement that allows its subsequent uses to increase the selected code, eg. it first selects a SELECT statement, and then the ALTER/CREATE VIEW statement that statement is the part of.

However, it has a small glitch, depending on which part the caret is currently placed. If it is in the SELECT statement, it's OK to only select that one. But it doesn't work as expected when in the following places:
- if it is in a string literal, it doesn't select anything at all
- if it is in the ALTER/CREATE, it only selects the SELECT statement

Check this short video here.

I haven't checked with other statements and levels (CREATE PROCEDURE, IF THEN ELSE structures or BEGIN END structures), but I'd expect the same inconsistent behavior there as well.

Thank you very much for report this bug and the demonstration.

Here is the tracking id for this bug #SA0037137

Another unexpected behavior, shown in this video here.

1. Having the caret in the middle of the statement works well.
2. Having it at the end of the statement without the terminator semicolon with the previous statement not having its own terminator semicolon present will make it select the previous statement instead of the current one.
3. Having it at the end of the statement after its terminator semicolon and with the previous statement not having its own terminator semicolon present will not select anything.
4. Having it at the end of the statement without a terminator semicolon with the previous statement having its own terminator semicolon present is okay.
5. Having it at the end of the statement after the terminator semicolon immediately after writing that semicolon with the previous statement having its own terminator semicolon present is also okay. If you move the caret away and then move it back after the semicolon, it won't work.