This is so well done, I'm kind of sad that it isn't getting more attention. I love the concept. My one bit of feedback is that the SQL query text area should have a button to execute the query, rather than clearing the results table and analyzing the query as I type. In the exercise on updating records, it was difficult for me to write the UPDATE statement because I wanted to look at the rows I was updating. I'd prefer if it left the results from the previous query up until the next query runs. Or if you could just leave the same results up the whole time and you could visually see the update run and highlight the rows/columns that were updated and see the values change in place.
Thanks for the kind words and feedback! I'll try and make the rows more static for some of the lessons -- it's tricky because I feel like the responsive interactivity is important when learning to write queries, but it just might not make sense for some of the lessons (like the update, as you mentioned). Really appreciate the feedback!
Ok, I think I've found a good solution on the updating, it should only update when you have a valid query now. Hopefully, it should be a bit more stable. :)
I love the instant feedback when completing a valid query, but as suggested, it can get in the way when trying to compose a filter. Perhaps use a `tickbox` to toggle the automatic table data update?
Another thing, the invalid / incomplete query alert gets in the way of looking at the last data row. Perhaps you can find a better location to show this alerts?
Thanks for the feedback, I've had the same thought about the popup, so maybe I can move it into the edit text. Otherwise, the result stability issue is important so I'm going to take another crack at it today. Thanks!
