To refresh, here's an example of what it would look like:
But I have also gotten some feedback from more than one source that this may not actually be as valuable as it may first appear. The reason is that, and this makes sense, the actual work flow when building SQL for your application is as follows:
- Open SQL tool and write your query
- Execute, evaluate results, modify, repeat
- Copy and paste final SQL into your editor
What are your thoughts? Can you explain to me why SQL editing features in the code editor is valuable, if generally SQL is composed in a SQL tool/editor?
One thing we've talked about is enabling testing from within the code editor. But it's not clear what this would look like. We would need to be able to build up an executable SQL statement from SQL that contains substitution variables and may even be a concatenation of multiple strings. I suppose it's possible, but it seems complicated and error-prone.
I suppose one simplistic approach is the following flow:
- In your editor, write a full SQL statement as a string
- right-click and choose "Test SQL" (or run a hot key) to let you test the SQL string right there in the application editor
- refine, retest
- modify the SQL to use substitution variables
So, what are your thoughts? Your feedback much appreciated.