All you need is PostgreSQL (ebellani.github.io)
from cm0002@toast.ooo to programming@programming.dev on 26 Jun 22:15
https://toast.ooo/post/14741867

#programming

threaded - newest

Valmond@lemmy.dbzer0.com on 26 Jun 22:24 next collapse

Or SQLite for embedded systems, and a NoSQL for no-sql, and MariaDB for FOSS DB.

Did I forget anything?

atzanteol@sh.itjust.works on 26 Jun 22:38 next collapse

And Oracle if you have way too much money just kicking around.

terabyterex@lemmy.world on 26 Jun 23:08 next collapse

if tpu give rhat money to oracle you are finding an extreme facist who believes our entire life should be recorded by the government and stored on oracle servers. he honestly said it will get rid of crime since you will alwaus be watched.

seblin@lemmy.world on 26 Jun 23:42 collapse

Even if I was a *illionaire I’d rather gargle lava rocks than touch Oracle with a mile long pole

Fedop@slrpnk.net on 27 Jun 03:47 next collapse

And DuckDb for columnar data storage

Valmond@lemmy.dbzer0.com on 27 Jun 06:36 collapse

Like an excel sheet?

MonkderVierte@lemmy.zip on 27 Jun 08:25 collapse

Orbitdb for p2p. Also, XML.

sin_free_for_00_days@sopuli.xyz on 26 Jun 22:57 next collapse

Seems, at a cursory look, to be a pretty solid intro to PostgreSQL. As @Valmond@lemmy.dbzer0.com commented, people sleep on SQLite. I think a lot of people skip SQLite because they think they need more. Hell, just about all my personal uses are covered with GNU recutils.

TehPers@beehaw.org on 27 Jun 00:12 next collapse

I swear Postgres always has new features whenever I look at it again.

I was building a system for long running durable job queues with multiple workers and of course Postgres has a solution for that. You can do row-level locking in a transaction to “reserve” jobs for the duration of that transaction, and you can use SKIP LOCKED to skip over reserved jobs so workers don’t block each other. There’s also LISTEN and NOTIFY if you want pub/sub to track when jobs complete, for example.

MonkderVierte@lemmy.zip on 27 Jun 08:22 collapse

Postgres has scope creep?

TehPers@beehaw.org on 27 Jun 08:29 collapse

The row-level locking and SKIP LOCKED seem like appropriate features for a SQL-based DBMS. I find it odd that it’s not more common, actually. Even MSSQL doesn’t make any promises about locking just a row and might decide to lock a whole page instead, from what I read anyway.

NOTIFY/LISTEN might be scope creep though. I’m not really sure what led to it being implemented.

sxan@midwest.social on 27 Jun 03:11 collapse

I hate admining PostreSQL, and groan when some app I want to use requires it. Don’t get me wrong: in a corp environment where someone else is responsible for backup/restore and permissions, pgsql > *. Tooling for it is great. It has every feature. But if I have to maintain it myself, I’ll chose a single file to copy and back up every time: sqlite FTW.

dallen@programming.dev on 27 Jun 04:53 collapse

CloudNativePG with barman backups makes it quite manageable.

towerful@programming.dev on 27 Jun 08:01 collapse

Yes. Not wanting to deal with more than a single file for backup/restore of your service?
Use kubernetes.

That doesn’t quite track