Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bluesky migrates to single-tenant SQLite

github.com

Post reply on HN
Print view View original

171–180 of 247 posts

Re: Bluesky migrates to single-tenant SQLite

#171

Post by abbbi »

malkia wrote: post #16

What do they mean by "Since SQLite does not support concurrent transactions" - it supports them, as long as you don't access the .db file through a file share (UNC, or NFS, etc) - https://www.sqlite.org/wal.html I've been using this to update/read db from multiple threads/processes on the same machine. You can also do snapshotting with the sqlite backup API, if you want consistent view, and to not hold on transaction…

it works if there is low traffic, as soon as you got bigger transactions or the amount of concurrent writes becomes heavier, you will at some point (even with WAL enabled) get "database locked" issues. You can work around that on application level to a certain point, but in general, if you are at that point, you should really consider using another database backend.

Re: Bluesky migrates to single-tenant SQLite

#172

Post by rockwotj »

gigatexal wrote: post #149
viraptor wrote: post #119

Earlier quoted context omitted.

> If you are doing a data migration and failed to account for some unexpected data, now you have people on different schema versions until you figure it out. That shouldn't be a big issue. Any service large/complex enough to care does the schema upgrades in phases, so it's 1. Make code future compatible. 2. Migrate data. 3. Remove old schema support. So typically it should be safe to run between steps 1 and 2 for a l…

> That shouldn't be a big issue. Any service large/complex enough to care does the schema upgrades in phases, so it's 1. Make code future compatible. 2. Migrate data. 3. Remove old schema support. Exactly this, schema migrations should be an append, deprecate, drop operation over time.

I wish there were ways to enforce this on the db so you never accidentally grabbed a table lock during these operations.

definitely have shot myself in the foot with postgres on this

Re: Bluesky migrates to single-tenant SQLite

#173

Post by moron4hire »

caskstrength wrote: post #155
gonzo41 wrote: post #36

Earlier quoted context omitted.

Commit and push often. Put a novel explaining yourself in the PR. And that's enough IMO.

> Commit and push often. Put a novel explaining yourself in the PR. And that's enough IMO. Someone reading the git changelog 5 years down the line most likely wouldn't be able to find your "novel" in the PR and definitely won't appreciate if instead of a "novel" you ended up with a "short call" with the assigned reviewer explained what you actually did in your 50 "wip" commits.

Someone reading 5 year old git logs is lost to begin with.

Re: Bluesky migrates to single-tenant SQLite

#174

Post by caskstrength »

moron4hire wrote: post #173
caskstrength wrote: post #155

Earlier quoted context omitted.

> Commit and push often. Put a novel explaining yourself in the PR. And that's enough IMO. Someone reading the git changelog 5 years down the line most likely wouldn't be able to find your "novel" in the PR and definitely won't appreciate if instead of a "novel" you ended up with a "short call" with the assigned reviewer explained what you actually did in your 50 "wip" commits.

Someone reading 5 year old git logs is lost to begin with.

When debugging I routinely explore git blame and read the changelog. This sometimes leads to 3, 5 or even 10 years old code. Doesn't mean I'm lost.

Re: Bluesky migrates to single-tenant SQLite

#176

Post by vehemenz »

anonyfox wrote: post #131

Slightly related: is Bluesky moderated good enough or do I get lots of rightwing and conspiracy crap like on twitter currently? I‘d really love to have some more civilized hub again that isn’t full of hate and anti-intellectualism.

It's anti-intellectual and uncivilized, but not because of rightwing conspiracy content. There is a strong culture of intolerance and censorship of viewpoints that diverge from the norm.

Re: Bluesky migrates to single-tenant SQLite

#177

Post by Hamuko »

victorbjorklund wrote: post #127

Can someone that knows more about bluesky explain what data is stored in sqlite and not? Because i assume it isnt messages etc between users.

By messages, do you mean direct messages (private messages between two parties)? Because Bluesky doesn't have those at the moment. There's only public messages broadcast to the world.

Haven't done any research to determine if there are plans for direct messages.

Re: Bluesky migrates to single-tenant SQLite

#179

Post by Hamuko »

ukzwc0 wrote: post #43
readline_prompt wrote: post #34

Earlier quoted context omitted.

don't know why, but recent teams around me have always made strict rules about number of commits in PRs. I just wanted to tell them the same thing you said: "Why don't you just look at the diffs?" curious for other opinions. (sorry not really about this particular topic)

A good practice is to rebase your commits before creating a PR into a single commit. You are free to commit as many times as you want to while doing your work. This minimizes the noise in the log.

It's only a good practice if the PR is a single logical change.

Re: Bluesky migrates to single-tenant SQLite

#180

Post by _heimdall »

anonyfox wrote: post #131

Slightly related: is Bluesky moderated good enough or do I get lots of rightwing and conspiracy crap like on twitter currently? I‘d really love to have some more civilized hub again that isn’t full of hate and anti-intellectualism.

Are you assuming that hate and anti-intellectualism are exclusively a rightwing thing?
Post reply on HN