zlacker

[return to "Pipe Syntax in SQL"]
1. Cianti+06[view] [source] 2024-08-24 16:16:12
>>legran+(OP)
Here is one example from the PDF:

    FROM r JOIN s USING (id)
    |> WHERE r.c < 15
    |> AGGREGATE sum(r.e) AS s GROUP BY r.d
    |> WHERE s > 3
    |> ORDER BY d
    |> SELECT d, s, rank() OVER (order by d)
Can we call this SQL anymore after this? This re-ordering of things has been done by others too, like PRQL, but they didn't call it SQL. I do think it makes things more readable.
◧◩
2. thiht+do[view] [source] 2024-08-24 18:38:50
>>Cianti+06
Honestly SQL screwed things up from the very beginning. "SELECT FROM" makes no sense at all. The projection being before the selection is dumb as hell. This is why we can’t get proper tooling for writing SQL, even autocompletion can’t work sanely. You write "SELECT", what’s it gonna autocomplete?

PRQL gives me hope that we might finally get something nice some day

◧◩◪
3. akira2+io[view] [source] 2024-08-24 18:39:26
>>thiht+do

    SELECT 1+2;
FROM clauses aren't required, and using multiple tables in FROM doesn't seem to work out too well when that syntax is listed first.
◧◩◪◨
4. yen223+ky[view] [source] 2024-08-24 19:56:44
>>akira2+io
WITH clauses are optional and appear before SELECT. No reason why the FROM clause couldn't behave the same
◧◩◪◨⬒
5. akira2+RD[view] [source] 2024-08-24 20:45:38
>>yen223+ky
Isn't that strictly for CTEs? In which case, you are SELECTing from the CTE.
[go to top]