Execute SQL statement at cursor location

[kburtram]

No description provided.

[coveralls]

Coverage increased (+0.1%) to 65.301% when pulling 6391f29 on feature/execStmt into 0007730 on master.

[benrr101]

Overall, I think this looks pretty decent. Take a look at my question/comment for the onRunQuery method, but otherwise, I think this is fine.

[benrr101]

I'm not certain on how this is supposed to work. Isn't the contract to send a line and column number? If so, how does the start/end position play into this?
I think it might be a bit cleaner to factor out the prompting/retry logic and have two onRunQuery methods, one for a single statement, one for a selection/entire doc.

[kburtram]

@benrr101 I've refactored that code that to make it more clear what's going on. When there is no selection range the editor selection property gives the cursor position, otherwise we use the start position in the selection as the cursor position.

[coveralls]

Coverage decreased (-4.1%) to 61.063% when pulling ea08bf6 on feature/execStmt into 0007730 on master.

[coveralls]

Coverage increased (+0.007%) to 65.204% when pulling c95cffd on feature/execStmt into 0007730 on master.

[coveralls]

Coverage decreased (-0.3%) to 64.944% when pulling a4dd5a2 on feature/execStmt into 0007730 on master.

[coveralls]

Coverage decreased (-0.3%) to 64.935% when pulling 2395b75 on feature/execStmt into 0007730 on master.

[coveralls]

Coverage decreased (-0.2%) to 64.974% when pulling a025144 on feature/execStmt into 0007730 on master.