17
top 30 comments
sorted by: hot top controversial new old
[-] JoMiran@lemmy.ml 10 points 3 weeks ago

MySQL belongs to Oracle. That's literally all you need to.know in order to avoid it.

[-] anomnom@sh.itjust.works 3 points 3 weeks ago

Isn’t that the point of Postgresql. It’s basically an open source version of MySQL.

I’m sure there are some proprietary nonsense that MySQL has, but I’ve never needed it in 17 years

[-] sobchak@programming.dev 6 points 3 weeks ago

Postgres is basically an open source version of Oracle DB. Much more featureful than MySQL. I believe Oracle bought MySQL just to kill it.

[-] Eyekaytee@aussie.zone 1 points 3 weeks ago

afaik MariaDB is the open source version of MySQL

[-] FlowerFan@piefed.blahaj.zone 2 points 3 weeks ago

how did the joke go? "one rich asshole called larry ellison"?

Why would anyone ever choose mysql over postgres?

[-] melfie@lemy.lol 3 points 3 weeks ago* (last edited 3 weeks ago)

Oracle sees itself as an activist organization, one whose goal is the advancement of the Israeli colonization project. Safra Catz, the company’s Israeli-American CEO, bluntly explained that any employees uncomfortable with supporting a genocide should simply quit. “We are not flexible regarding our mission, and our commitment to Israel is second to none” (source)

Hmm, MySQL or PostgreSQL—how will we ever decide which one to pick.

[-] slacktoid@lemmy.ml 3 points 3 weeks ago

Stop using mysql, you have postgres.

[-] possiblylinux127@lemmy.zip 2 points 3 weeks ago
[-] immobile7801@piefed.social 4 points 3 weeks ago

FWIW mariadb was bought by a private equity firm in 2024

[-] psoul@lemmy.world 2 points 3 weeks ago

Oh no… it was the easy solution for Wordpress and other plug and play self hosted services .

[-] call_me_xale@lemmy.zip 3 points 3 weeks ago

Hell, even SQLite is good enough for most small projects.

[-] dan@upvote.au 1 points 3 weeks ago* (last edited 3 weeks ago)

SQLite is underrated. I've used it for high traffic systems with no issues. If your system has a large number of readers and a small number of writers, it performs very well. It's not as good for high-concurrency write-heavy use cases, but that's not common (most apps read far more than they write).

My use case was a DB that was created during the build process, then read on every page load.

[-] derpgon@programming.dev 1 points 3 weeks ago

Wow, I never thought about storing build data in an SQLite file. That's quite clever.

[-] dan@upvote.au 3 points 3 weeks ago* (last edited 3 weeks ago)

One of SQLite's recommended use cases is as an alternate to proprietary binary formats: https://sqlite.org/appfileformat.html. Programs often store data in binary files for performance, but you get a lot of the same functionality included with SQLite (fast random access, concurrent usage, atomicity, updates that don't need to rewrite the whole file, etc) without having to implement a file format yourself.

I'm not sure if this is still the case, but Facebook'a HHVM used to store the compiled bytecode for the whole site in a single SQLite database: https://docs.hhvm.com/docs/hhvm/advanced-usage/repo-authoritative/. Every pageload loaded the bytecode for all required files from the DB.

[-] hoppolito@mander.xyz 1 points 3 weeks ago

Fascinating read, I should definitely also make way more use of sqlite for little side projects.
Thanks for the link!

[-] 0x0@lemmy.zip 1 points 3 weeks ago

They also have a (one-time fee) encryption extension.

[-] MrSoup@lemmy.zip 1 points 3 weeks ago* (last edited 3 weeks ago)

MariaDB >>>

I've been using it since ever on my rpi because they say it's easier on resources

[-] 0x0@lemmy.zip 1 points 3 weeks ago

No one should be using MySQL since 2010.

[-] dan@upvote.au 1 points 3 weeks ago

MariaDB is not always a drop-in replacement. There's several features that MySQL has that MariaDB doesn't, especially related to the optimizer (for some types of queries, MySQL will give you a more optimized execution plan compared to MariaDB). It's also missing some newer data types, like JSON (which indexes the individual fields in JSON objects to make filtering on them more efficient).

MariaDB and MySQL are both fine. Even though MySQL doesn't receive as much development any more, it doesn't really need it. It works fine. If you want a better database system, switch to PostgreSQL, not MariaDB.

[-] schnurrito@discuss.tchncs.de 0 points 3 weeks ago

Are there real advantages to using either MySQL or MariaDB instead of PostgreSQL?

No. But there are a number of advantages of using PostgreSQL over the others.

[-] kumi@feddit.online 1 points 3 weeks ago* (last edited 3 weeks ago)

Operating and securing Postgres is a steeper learning curve. MariaDB is more forgiving for best-effort shoestring setups without compensating scalability for it.

As a dev I'm agnostic, as an owner and computer scientiest I prefer Postgres, as a sysadmin or *Ops I will put my hand up for MariaDB any day if I'll be on call or maintain deployments.

[-] Rikj000@discuss.tchncs.de 1 points 3 weeks ago

Yeah,
I did a speed test comparison between Oracle MySQL and MariaDB MySQL,
MariaDB is about 10 times faster.

FYI: When Oracle bought MySQL a lot of developers left and created MariaDB, so the brains behind the project moved, and in the meantime Oracle did a great job of fucking things up.

[-] schnurrito@discuss.tchncs.de 0 points 3 weeks ago

That's not what I asked. I asked about a comparison of both of them to PostgreSQL.

[-] Rikj000@discuss.tchncs.de 1 points 3 weeks ago

Oh misread my bad,
not much experience with PostgreSQL

[-] fizzle@quokk.au -2 points 3 weeks ago

I didn't know this was ever in question?

Also stop calling it "my sequel"

[-] TrickDacy@lemmy.world 1 points 3 weeks ago

stop calling it "my sequel"

Why?

[-] frongt@lemmy.zip -2 points 3 weeks ago

Sequel is Microsoft. S-Q-L is Linux.

[-] surewhynotlem@lemmy.world -1 points 3 weeks ago

Microsoft's is "squeal". Like a pig. When you get the bill.

this post was submitted on 11 Jan 2026
17 points (100.0% liked)

Selfhosted

56092 readers
59 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS