Well the question you saw coming (hopefully) - how does it compare to Prisma use cases?
One thing I really like about Prisma is only updating my schema and having migrations generated as the "diff".
One thing I really like about Prisma is only updating my schema and having migrations generated as the "diff".
As far as migrations go, pg-nano is taking the same “schema diffing” approach that I assume Prisma does, where the active schema of your Postgres instance is compared to the desired schema (defined via SQL files in pg-nano's case) and a migration plan is generated from there. In the context of migrating a non-local Postgres instance, pg-nano still has some R&D to do.
The main thing holding me back from Prisma is precisely what you like about it - if the migrations are auto-generated and I can't edit them afterward, I won't be able to do what I need to.