Closed justinclift closed 1 year ago
Addressed this for both pages in: https://github.com/sqlitebrowser/dbhub.io/commit/ca389d4a58fa7795ab2de610e5a7bda6615c9a41
Also fixed a few other minor issues on both pages at the same time.
Haven't pushed the new code to production yet, so will leave this issue open for the time being.
This fix is now live. :smile:
Just noticed that when we try to "Run SQL" with an empty input it gives a silly error message that doesn't really make sense for empty input.
We should catch this specific case, and do something reasonable with it.
Similar for the Execute SQL page, which has a similar problem.