8 ms·

Took me a while to discover the SQL can be edited...

• afiodorov 2y ago
  Sorry about that. I prefer for my UI to be discoverable. P.S. We can share links too https://www.imdb-sql.com/?query=select+1 https://www.imdb-sql.com/?query=select+1 The SQL flavor is https://duckdb.org/docs/sql/query_syntax/select https://duckdb.org/docs/sql/query_syntax/select
  • Pikamander2 2y ago
    > I prefer for my UI to be discoverable. I'm not quite sure what you mean by this. If you gave the SQL a light gray border and perhaps overflow-y:scroll, it would make it much more obvious that it can be edited directly without needing any other adjustments.
    • afiodorov 2y ago
      Thanks for the suggestion, will try to improve soon. If anyone with actual css experience wants to open a PR in the meantime I'll be very happy!
      • _thisdot 2y ago
        Taking a look right now. I found the source code from another comment in this HN thread. Would be better if you linked it in app
        • afiodorov 2y ago
          Shouldn't be hard to find since the repo name on github is same as the domain :). I just run npm run dev locally. You'll need the parquet file of the data in public/ though, can get it from http://www.imdb-sql.com/imdb01-11-2024.parquet http://www.imdb-sql.com/imdb01-11-2024.parquet
    • afiodorov 2y ago
      done
• srmarm 2y ago
  Yeah, I also struggled with the purple box - I assumed I'd change the options, click run and it'd reload the data accordingly. Almost quit before I realised you have to build and then run. If the changes in the purple box were reflected in the SQL code preview that would be much better. That being said it's an impressive demo of what the browser can do without breaking a sweat! Will try and discover some new stuff to watch now!
  • afiodorov 2y ago
    Browsers are becoming OS'es :).