Href Https

Evidence

• Show HN: Wtdb – give every Git worktree its own database — I run a lot of agentic coding sessions in parallel, each in its own git worktree. Every worktree points at the same local Postgres though, so the moment one branch runs a migration it changes the schema out from under the others. I'd end up with agents tripping over each other, or me babysitting which branch "owned" the DB at any given moment.<p>I made this to fix it. I hope you might find it helpful too.

  HACKER_NEWS

• SQLite-utils 4.0, now with database schema migrations

  HACKER_NEWS

• Show HN: Pgmig: Generate migrations between Postgres databases — I've been comparing PostgreSQL schemas for so many years now. I've been using all kinds of frameworks for ORM and code-first schema generation, but getting the actual "diff" between what I have and what I want has always been a pain.<p>For a long time, I've relied on a customized version of migra (<a href="https://github.com/djrobstep/migra" rel="nofollow">https://github.com/djrobstep/migra</a>). It was the best tool of all those I've tried, but it's unfortunately deprecated and no longer maintained.<p>I kept dreaming of building my own comparison tool - one with modern features, better performance, and the extra features I always wished I had.<p>I've had the architecture of the tool in my head for years, but knew that I will never find the time to do the tedious introspection query logic. Last weekend I decided to finally give it a try and built an initial version with Claude. Long story short it's now stable enough that I'm using it in all my personal and work projects that use PostgreSQL.<p>This experience really shifted my thinking in regards to building stuff with AI, and the future of tooling in general.<p>Excited to get any feedback, let me know what you think!<p><a href="https://github.com/Apakottur/pgmig" rel="nofollow">https://github.com/Apakottur/pgmig</a>

  HACKER_NEWS