I was really excited when Prisma1 came out. It would be understatement to mention that Prisma1 was way overpromised and nothing ever materialised.
With Prisma2, honestly disappointed as it is too little to show for. This is an ORM like library that supports only couple of databases with database migrations still in experimental state with broken links for workarounds[1]
After working with TypeORM in a quite few projects I can tell that there're a lot of things that are wrong with it. And TypeORM absolutely doesn't provide "full feature support" for all 8 databases. Even some basic things are missing, like joins on delete sql queries in query builder. Simple 'set' mysql datatype support was missing and I had to add it myself. When it comes to mapping and data modeling, things are OK most of the time but it breaks when it comes to somewhat non-basic stuff like STI. Don't get me started on bugs. Any reasonable alternatives and orm developments are welcome and Prisma2 doesn't take away anything, it's a free software.
TypeORM seems wonderful for basic stuff, but also in dire need of maintainers/contributors, at least based on its GitHub issues and docs [0] to get that last 20% (that takes just as much time as the first 80%).
It's actually really good but I don't get the feel of wonder after all those years together anymore :) Huge db and feature scope definitely keep it away from any particular completeness despite size and age of the project. Hope to see something more focused @next.
I experienced many kinds of problems with TypeORM, including data corruption and lost. Before using it in a project I strongly suggest taking a look around its issues or at least reading the issue about its future [0].
On the other side my experience with Prisma 2 so far has been excellent and I found a very good community around it.
Im using TypeORM and happy to learn if it is so. Can you please show any relevant issues for it ?
It would be interesting to understand how data corruption and lost happens at ORM level!
The gist of this conversation is - passionate open source devs outdo many folds in their work yet fail to monetise their work. And a VC backed company here has little to show for apart from they've managed to trend in HN!
The issue title mentions the sync feature but the same happened with migrations and I don't want code randomly dropping data from my database even if it is in a development environment anyway. But that is not the point because no one would run automatic code like this on production data without some kind safety net. The point I was trying to make is "listing features as non beta doesn't make them stable". As far as I am concerned the alpha preview of Prisma 2 has been far more stable than every other version of TypeORM I had to work with.
> I was really excited when Prisma1 came out. It would be understatement to mention that Prisma1 was way overpromised and nothing ever materialised.
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. At that point, we needed to make a tough judgement call and decided to rewrite Prisma in Rust. Needless to say that this was quite a challenge, but our engineers have done an absolutely outstanding job of managing this 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. 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!
> With Prisma2, honestly disappointed as it is too little to show for. This is an ORM like library that supports only couple of databases with database migrations still in experimental state with broken links for workarounds[1]
Please recall that we're just launching into Beta. 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!
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. cascading deletes [1]) and using those with Prisma Client. (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).
With Prisma2, honestly disappointed as it is too little to show for. This is an ORM like library that supports only couple of databases with database migrations still in experimental state with broken links for workarounds[1]
Also Prisma2 has half of the features at 'No / Not yet' supported state - https://www.prisma.io/docs/reference/database-connectors/dat...
Well makes me wonder what's wrong with TypeORM which supports 8 different databases with full feature support and migrations that work!
[1] https://www.prisma.io/docs/reference/tools-and-interfaces/pr...