5 ms·
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
by esistgut 6y ago
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.
[0] https://github.com/typeorm/typeorm/issues/3267 https://github.com/typeorm/typeorm/issues/3267
- samblr 6y ago>> including data corruption and lost 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!
- esistgut 6y agohttps://github.com/typeorm/typeorm/issues/3636 https://github.com/typeorm/typeorm/issues/3636 this is last one I encountered before abandoning TypeORM.
- hau 6y agoTo be fair sync feature is marked as unsafe to use in production in documentation.
- esistgut 6y agoThe 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.