o11c@programming.dev 1 year ago
This is about the one thing where SQL is a badly designed language, and you should use a frontend that forces you to write your queries in the order (table, filter, columns) for consistency.
UPDATE table_name WHERE y = $3 SET w = $1, x = $2, z = $4 RETURNING * FROM table_name SELECT w, x, y, z
jjjalljs@ttrpg.network 1 year ago
I get mildly mad all the time when writing SQL because I feel like it’s upside down
Instead of
where the columns are referenced before they’re defined (like what is u.id? Keep reading to find out!)
it should instead be
Now nothing is defined before it’s used, and you’re less likely to miss your where clause. I usually write the joins first anyway because I know what tables I care about, but don’t know which specific things I’ll want.
I can’t think of any other languages that use things before they’re defined except extremely dysfunctional JavaScript.
lakemalcom10@lemm.ee 1 year ago
You might enjoy github.com/max-sixty/prql
JWBananas@startrek.website 1 year ago
From the cabinet, get a cup.