4 ms·
Sad but true. Or they learn "something" about SQL but not about indexes, data types, joins, or even aggregate functions. I've seen some python horror shows that
by icedchai 1y ago
Sad but true. Or they learn "something" about SQL but not about indexes, data types, joins, or even aggregate functions. I've seen some python horror shows that would select * entire tables into lists of dicts, only to do the equivalent of a where clause and a couple of sums.
- _ea1k 1y agoOuch. I was really hoping this wasn't so common, but I guess it is. I'm sure they heard somewhere that "joins are expensive" or something along those lines, so they solved it!
- solid_fuel 1y agoPrisma built a whole ORM around that, complete with the client-side joins.
- icedchai 1y agoThere are also other "lets pretend we have big data" patterns I've seen. Running something like AWS Athena or Hadoop over and over, for less than a couple gigs of data that would fit into memory on a laptop from 15 years ago.
- joseda-hg 1y agoClassic, I remember seeing something like this SELECT * FROM X, into a C# list, Filter it with LINQ, and then use C# to do calculations "Why not EF?" "Someone told me it was slower"