After a morning of slow query logging and cussing, a misplaced "GROUP BY" that was turning a 0.04 second query into one that took over fifteen seconds has been fixed. I'll leave the slow query log running overnight though just to make sure I didn't miss any less common ones. If you're still seeing any serious site slowdowns, let us know.
(Score: -1, Flamebait) by Anonymous Coward on Tuesday January 08 2019, @05:32PM (6 children)
Nosql is the clear answer. Group by clauses, set theory, and the relational model are for old white incels. Soylent should be hip and diverse and web-scale!
(Score: 2) by Freeman on Tuesday January 08 2019, @06:08PM (5 children)
Oh, you mean, they should find some way to use an excel spreadsheet for all their database needs?
Joshua 1:9 "Be strong and of a good courage; be not afraid, neither be thou dismayed: for the Lord thy God is with thee"
(Score: 3, Funny) by khallow on Tuesday January 08 2019, @08:34PM (4 children)
(Score: 0) by Anonymous Coward on Tuesday January 08 2019, @08:46PM (3 children)
CSV
works for me!
(Score: 2) by The Mighty Buzzard on Tuesday January 08 2019, @11:46PM (2 children)
Let's try the lost art of compromise. CSV in an Excel spreadsheet. Best to be on the safe side and encapsulate it in XML too.
My rights don't end where your fear begins.
(Score: 4, Funny) by maxwell demon on Wednesday January 09 2019, @06:45AM (1 child)
But only if the XML is encapsulated in JSON.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 0) by Anonymous Coward on Wednesday January 09 2019, @11:02AM
Fine, so long as you then serialize it with YAML [wikipedia.org]