Doing things with raw sql should be just as fast as using a library. Django does some bits well but it's insanely slow at times. Make it very easy to debug the generated sql for perf reasons. Access foreign relationships as promises (always). It makes it easy to diff and bisect when things fo awry.ģ) Super light weight Object -> sql. But again don't do fancy node modules, have the typescript types committable to git repo. Don't do smart fancy node modules either.Ģ) autogenerated typescript types, this are nice. Django migrations are a giant pain in the ass. This lets me have my state of schema committed to git, and easily move from dev -> staging -> prod. The fact that the returned objects are plain old javascript objects (POJOs) that's nice.īasically all I want is a lightweight layer that exposes a promise api to deal with different databases in a uniform manner.ġ) sync to schema.json (this json file contains info of all tables, their columns, indices and foreign keys). To put it in the words of our CEO: we'd be more than happy to embrace whatever package manager mechanism would enable this use case 'more cleanly'. This doesn't get easier by the variety of package managers out there and the custom workflows they sometimes employ (e.g. The gist is that we're very open to other approaches but this was the best we've come up with so far after 9 months of experimentation and lots of feedback from the community. The reason why we made it the default is because it comes closest to what Node.js developers are used to and therefore fits their workflow and mental model nicely.Īlso please read this Twitter thread between the lead Yarn maintainer and our CEO. Hey there, thanks a lot for the feedback! As I mentioned in other threads, you can configure the output location for the generated Prisma Client library, node_modules is just the default. (While these features are not supported by Prisma Migrate yet, you can still configure them in your DB and use Prisma Client for DB access). cascading deletes ) and using those with Prisma Client. Sorry about the broken links, I'm in the process of fixing most of them! In this case, the links point to the 'Guides > Database workflows'-section which contains a number of helpful step-by-step tutorials for performing certain schema migrations (e.g. As I said, we now have the foundation to expand the functionality of our tools! You'll see a lot of exciting improvements and new tools from Prisma over the next few months! Please recall that we're just launching into Beta. This is an ORM like library that supports only couple of databases with database migrations still in experimental state with broken links for workarounds > With Prisma2, honestly disappointed as it is too little to show for. I'm really proud of the result though, we've built a strong and stable foundation that allows us to expand the functionality of our tools over time – this would not have been possible without the rewrite! We certainly had a number of tough learnings, especially when it came to the variety of different DB schemas out there that we needed to support with our introspection. Needless to say that this was quite a challenge, but our engineers have done an absolutely outstanding job of managing this rewrite. At that point, we needed to make a tough judgement call and decided to rewrite Prisma in Rust. While I can understand your sentiment, I don't think this is quite true! We've seen a number of companies very successfully adopt Prisma 1 – ultimately we realized though that the vision of building a new way for application developers to access their database can't be built on top of the JVM. It would be understatement to mention that Prisma1 was way overpromised and nothing ever materialised. I was really excited when Prisma1 came out.

Prisma app news