Hacker News Reader

Comment by raxxorraxor | Hacker News Reader

SQLite is simple in its own way and I like the design principle of their SQL dialect.

"Right joins are just left joins in the wrong direction, you don't need that crap"

Of course it always gets simpler or more specialised. I think many apps using databases would run with SQLite just as well. And some would probably run just as well with a textfile instead of any db like SQLite.

View on HN

> "Right joins are just left joins in the wrong direction, you don't need that crap"

SQLite has supported all types of joins since version 3.39 in 2022.

Well, look at that, now it is downhill from here!

I must've messed something up, but I remember some joins (was it full outer join?) being unbelievably slow? Was I doing something wrong?

Too vague of a question to give you an answer you'll likely sound satisfactory :)

You probably just needed to create indexes over your data to speed things up.

For the love of god, don't do blank textiles anymore. In the end you have a software that has 20 (or more) individual files for each programs section, which works fine until you want the files to be consistent. Boom. And then you add a lock to fix it and suddenly your whole program can only run sequentially. And then your customers ask why it's so slow in ingress. I won't name any names here, but this is a real commercial product.

We use a cheap invoicing program. It works fine except it gets very slow when dealing with large numbers if invoices. Turns out each invoice (or payment record, or customer record, or whatever) is a separate text file with form-urlencoded data. No indices.

Reply on news.ycombinator.com