How the F**** does anyone use Prisma in production?
My company has been using Prisma in production for just over 2 years. We've definitely ran into pain points such as the lack of support for long-running transactions, but it provides an intuitive type-safe API for data access that makes iteration fast and easy. Plus, the tooling around GraphQL (namely Nexus) integrates really well in our stack. For 90% of our use cases Prisma does the job very well; for the other 10% we use a library called Slonik to roll our own SQL queries. So to answer the question in the title of this post, we use Prisma where it's convenient to do so, and then raw SQL with Slonik when we need more advanced functionality.
More on reddit.com`interactiveTransactions` feature breaks long running transactions
Urgent: Transaction Deadlocks and Timeouts Causing High CPU Usage
LRT: Interactive Transactions Epic
Batch inserts were not available without a preview flag until 3 days ago, database transactions absolutely suck (can't use the result of one insert in the input of another query in the same transaction). Aggregation is very limited.
Is anyone actually using Prisma in production or just waiting around for it to get better?
It's incredible how people add Prisma to their framework or boilerplate (see Blitz, Redwood, Bedrock) without realizing this.
In theory Prisma is great and I love the type safety it provides, but its NOT production ready cause its way too limited. The fact it doesn't properly support transactions alone is enough for me to never consider using it. It has been one disappointment after another ever since graph-cool
Hey, thanks for sharing your thoughts about Prisma!
Batch inserts were not available without a preview flag until 3 days ago
It's definitely true that we don't have all the features you could wish for in an ORM from the very beginning, but that's why we keep shipping new features every two weeks and have added a ton of new features just in Q1. You can also always check the upcoming features on our roadmap. (Also to be honest, I actually struggle to see your comment here as negative because I think it's great that we keep shipping these new features at all 😅).
If there's feature you're missing, it's very likely that we can ship it if you create feature request for it so that we can prioritize it in our planning.
database transactions absolutely suck (can't use the result of one insert in the input of another query in the same transaction)
I just responded in-depth (see this comment) about why we decided to not support long-running transactions in Prisma for now. So far, we haven't learned about compelling use cases for transactions that wouldn't be better solved with a dedicated API like bulk operations, nested writes, atomic operators, transaction batches or optimistic concurrency control. If you have a use case in mind that we're not yet covering, we'd love to learn about it! Would you be open to sharing it in a GitHub issue so that we can discuss how we can enable it via the Prisma Client API?
Aggregation is very limited.
As I mentioned before, Prisma is definitely not feature complete, but we are making fast progress and ship new features regularly. If there are features that you're still missing, you can always drop down to raw SQL and use Prisma Client's $queryRaw method. But if the majority of your queries need customization, you might indeed be better off with a lower-level query builder like knex.js or just use a plain DB driver like pg.
In fact, we wrote a page in our docs that lays out the tradeoffs for you to evaluate whether Prisma fits your use case: Should you use Prisma?.
If you need/want full control over all of your database queries, Prisma might indeed not be worth it for you because its strength lie elsewhere.
We have a problem with prisma that its own query for a real projects its long queries and not readable, not really maintainable.
I am asking for any soution over prisma to handle this cases. but not solutions with Sequalize or TypeORM.
roof melodic weather birds include bedroom march cooing fade encouraging
This post was mass deleted and anonymized with Redact