Focusing on a single db was not the original intent as migrations was a big reason why the ORM product category became (and still remains) popular.<p>As for performance, you are right. We do take a hit when trying to support as many DBs as possible. However, performance is not an issue. Take a look at <a href="https://benchmarks.prisma.io" rel="nofollow">https://benchmarks.prisma.io</a>. Regardless, we're always open to being given examples whereby we can dig into performance related issues. So if you have any, please send them our way.
I'm surprised about what you say regarding migrations. Personally I don't know any dev that uses automatic migrations even with extremely mature ORMs like Entity Framework.<p>> <i>performance is not an issue</i><p>No offense but I gotta say, those benchmarks look a bit off.<p>To begin with, why are you only comparing vs other ORMs instead of adding a baseline of handwritten SQL code?<p>Second, it's not clear how big the data set is. In the repo it seems the default size is 50 rows. Is that what you used for the results in the website?<p>Third, how can Drizzle take 1300ms to do such a lightweight query with a single join? Something is obviously wrong here considering Drizzle creates a single SQL query. Did you prepare the statements? Are you even using the latest version?<p>On top of that... it seems Prisma is taking +50ms to do a single join on two tables with 50 rows which means it would execute 20 queries per second. Not exactly performant.
We use Prisma in part due to its migration support, I want it to Just Work™ and not have to deal with writing manual migrations every time, it's a common feature request of many ORMs if they don't have it.