Re:
by hrmtst93837 on Wednesday March 18, 2026 @06:49AM
(#47423975)
SQLite is fine right up until you want concurrent writers. Once you need multiple users, cross-host access, or anything that looks like shared infra instead of a local cache, the file-locking model stops being cute and starts setting the rules for the whole design. For collaborative versioning, Postgres makes more sense.
[ Parent
| on HN ]
Re:
by brigandish on Wednesday March 18, 2026 @07:44AM
(#47424461)
For a distributed VCS, what would be the need for such things? Even if it were a really big project, how many writes could be going on that this becomes a bottleneck? I don't see it but maybe you have a situation in mind.
Re:
by ImGajeed76 on Wednesday March 18, 2026 @08:03AM
(#47424626)
The problem i faced is mostly importing large repos. But normal use should be fine.
Re:
by lelanthran on Wednesday March 18, 2026 @09:05AM
(#47425314)
In the current environment, even a distributed VCS may have concurrent agents modifying it on different branches.