pull down to refresh

7 replies \ @k00b OP 15 Mar \ on: SN release: independent territory and comment ranking, fix reply costs meta
Man I was cooking the DB's CPU for the last 4 hours with an index typo in this release.
CREATE INDEX IF NOT EXISTS some_idx ON some_table(some_value DESC NULLS LAST) is NOT equivalent to CREATE INDEX IF NOT EXISTS some_idx ON some_table(some_value DESC).
The site was feeling so slow for a second 4-hour there.
write
preview
44 sats \ 6 replies \ @SimpleStacker 15 Mar
👀
I wonder if you hate working with SQL as much as I do
reply
0 sats \ 5 replies \ @k00b OP 15 Mar
Relative to the alternatives, I love it.
I wrote a relational database from scratch in college for one of my classes (its the only assignment we were given). I get them. They're like a crazy best friend - crazy on the outside, deeply sane on the inside, irreplaceable.
There's a half century of research invested into them. Normal data is so so so so underestimated. (At least in applications like this.)
reply
21 sats \ 4 replies \ @SimpleStacker 15 Mar
Fair. I don't even really know what the alternatives are.
My background doesn't deal much with live data, so I'm mostly happy using pandas in python, but no one uses that for a production database.
reply
31 sats \ 3 replies \ @k00b OP 15 Mar
I'm sure someone uses a pandas franken-db in prod. I read a book about using ElasticSearch as a production DB.
reply
77 sats \ 2 replies \ @SimpleStacker 15 Mar
I think my beef with SQL is that wherever I've seen it used, complex queries are often written out entirely in a single chunk of code. Not sure if the language doesn't lend itself well to modularity, but these chunky queries always seemed hard to decipher and thus error prone.
reply
30 sats \ 1 reply \ @k00b OP 15 Mar
That's a great point. I took the lack of composability for granted. I'm sure there are awesome alternatives aimed at fixing that.
view all 1 replies