zlacker

IMO having SELECT before FROM is one of SQL's biggest mistakes. I would gladly welcome a new syntax that rectifies this. (Also https://duckdb.org/2022/05/04/friendlier-sql.html)

I don't love the multiple WHEREs.

>>richbe+(OP)
duckDB is what sql should be in 2024

https://duckdbsnippets.com/

>>richbe+(OP)
Duckdb also supports prql with an extension https://github.com/ywelsch/duckdb-prql

>>abelch+Xr
The very first example on that page is vulnerable to injection.

>>richbe+(OP)
That's a great list of friendlier sql in DuckDB. For most of that list I either run into it regularly or have wanted the exact fix they have.

>>xigoi+iH1
Which one?

>>richbe+1m2

  #!/bin/bash 
  function csv_to_parquet() {     
      file_path="$1"     
      duckdb -c "COPY (SELECT * FROM read_csv_auto('$file_path')) TO '${file_path%.*}.parquet' (FORMAT PARQUET);" }

>>xigoi+bo2
Eh, in the context of the site and other snippets that seems pedantic.

Could it be run on untrusted user input? Sure. Does it actually pose a threat? It's improbable.

>>richbe+(OP)
SQL was supposed to follow English grammar. Having FROM before SELECT is like having “Begun” before “these clone wars have.”