Earlier quoted context omitted.
Prisma supports transactions through the `prisma.transaction` API. This allow you to perform multiple DB actions in a single request and gives you an all-or-nothing semantic.
Thanks! IIUC, a "batch" request is run in a transaction.But if I need to run business logic in the middle of requests that's not supported?
Prisma Raises $12M Series A
111–114 of 114 posts
Re: Prisma Raises $12M Series A
#112I've been using prisma for a couple months now at my employer. The longer I use it, the more frustrated I find myself with the tool. Here's a list of a few things out of many that you can't do with this tool (Prisma Migrate): * Renaming columns/tables * Migrating data from one column/table to another column/table. * Write anything that isn't a table definition, such as procedures, functions, events, transactions, etc…
I'm with the Product team at Prisma, currently focusing on migrations.
We are currently working on improving Prisma Migrate to unblock some of the use cases you have suggested. While I am not sure our first production-ready version of Migrate will address all of the short comings you've listed, we think we'll able to solve the most important ones.
I encourage you to check out the new improvements I am sure we'll be releasing during the course of Q3.
If you have time, I'd love to do a call with you and dive deeper into these topics! You can find me on the community Slack for Prisma under the same username.
Re: Prisma Raises $12M Series A
#113I've been using prisma for a couple months now at my employer. The longer I use it, the more frustrated I find myself with the tool. Here's a list of a few things out of many that you can't do with this tool (Prisma Migrate): * Renaming columns/tables * Migrating data from one column/table to another column/table. * Write anything that isn't a table definition, such as procedures, functions, events, transactions, etc…
I think that declarative migrations don't make sense in the real world. You're modifying existing state so it has to be incremental. I'm curious to see how Prisma plans to handle these real-world use-cases.
I'm with the product team at Prisma, currently focusing on migrations.
You are right about the fact that declarative migrations introduces some design challenges that can be hard to solve. In the current version of Prisma Migrate, changes to the declarative schema file are translated to auto-generate incremental migration files.
We have a few ideas for how we can improve our system to better deal with these challenges. Please feel free to follow along or check back in a few months if you are interested in how we solve (or not?) these problems! :)
Re: Prisma Raises $12M Series A
#114I find it odd that they say "Prisma is ready for production", but "Prisma Migrate is currently in an experimental state and should not be used in production environments". Having a robust migration management system is one of the primary things I look for in an ORM/database management tool in general. The only constant is change when it comes to business requirements, and having the ability to easily and safely chang…
I'm with the product team at Prisma, currently focusing on migrations.
Your point is valid, hence delivering a production-ready solution for migrations is one of our top priorities.
However, as my colleague @nikolasburk shared above, you can use a third-party migration system (knex, node-pg-migrate, e al) with Prisma and still get all the benefits of Prisma Client.
Prisma is designed to be more powerful if you are using the entire toolkit, but we also want to make it easy to use just specific tools within the kit, if that is what works well for your project.
Feel free to follow along or check us out again in a few months and hopefully by then our migration system will no longer be any kind of friction point. :)