Hacker News Reader

Looks like the traditional caveats for ORMs would apply here. Many painful lessons have been learned in that field.

What would be interesting to see is the cost of change i.e. how de-coupled things are to make changes simple.

Changes like: Adding a field To changing a relationship between entities and such.

That's a good question. As long as you have additive changes, Prisma can do the change automatically for you. As soon as it's a change where anything will be dropped (field, relationship etc), Prisma will prompt you and ask if you want to perform that breaking change. The only command you need to know for data model changes is `prisma deploy`. Disclaimer: I work at Prisma.

As someone who has been using Prisma religiously for the past year, I would like to express that this is the largest pain point of working with the platform. Not having the ability to custom define these transformations is brutal.

That is great to hear! Because we're working on exactly fixing that! What is the concrete limitation you're hitting with that?

Reply on news.ycombinator.com