Live data from Hacker News

Bluesky migrates to single-tenant SQLite

github.com

31–40 of 247 posts

Re: Bluesky migrates to single-tenant SQLite

#31
post #29

That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior

I prefer to read the unified diff and commits don't matter as much.

This is the answer.

Re: Bluesky migrates to single-tenant SQLite

#32

That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior

Those two work very closely together, so probably not as nightmarish as it may appear to an observer. But, the two of them are most certainly warriors.

Re: Bluesky migrates to single-tenant SQLite

#33
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…

Probably means there’s still no row-level locking at least last I checked, very limited table-level locking. The writer still grabs a lock on entire db per docs

Re: Bluesky migrates to single-tenant SQLite

#34
post #29

That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior

I prefer to read the unified diff and commits don't matter as much.

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)

Re: Bluesky migrates to single-tenant SQLite

#35
post #29

That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior

I prefer to read the unified diff and commits don't matter as much.

Commit your code and commit it often. There's no reason not to.

Re: Bluesky migrates to single-tenant SQLite

#36
post #29

Earlier quoted context omitted.

I prefer to read the unified diff and commits don't matter as much.

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)

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

Re: Bluesky migrates to single-tenant SQLite

#37
post #29

Earlier quoted context omitted.

I prefer to read the unified diff and commits don't matter as much.

Commit your code and commit it often. There's no reason not to.

Commit and commit often, but then clean up the history into discrete, readable chunks.

If your PRs are tiny it's not a big deal, but with 190 files changed in this one, it absolutely should have been rebased into a more reasonable commit history.

Re: Bluesky migrates to single-tenant SQLite

#38
post #29

Earlier quoted context omitted.

I prefer to read the unified diff and commits don't matter as much.

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)

Squash is our git given right.

Re: Bluesky migrates to single-tenant SQLite

#39
post #29

Earlier quoted context omitted.

I prefer to read the unified diff and commits don't matter as much.

Commit your code and commit it often. There's no reason not to.

Also continuously integrate (from trunk) if you want to hit that moving target sooner.

Re: Bluesky migrates to single-tenant SQLite

#40
post #13
post #12

Is Bluesky still invite only?

Yes. I have invite codes if you would like one. Email in my profile. Edit: they're all gone!

Is your offer invite code available to other randoms like myself? I tried to register on bsky months ago and still haven't been approved.
Post reply on HN