Re:Prisma 2.0 Beta: Type-safe Database Access
by samblr on Wednesday April 01, 2020 @03:28AM
(#22746520)
>> 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!
Re:Prisma 2.0 Beta: Type-safe Database Access
by esistgut on Wednesday April 01, 2020 @07:00AM
(#22747472)
https://github.com/typeorm/typeorm/issues/3636 this is last one I encountered before abandoning TypeORM.
Re:Prisma 2.0 Beta: Type-safe Database Access
by hau on Wednesday April 01, 2020 @07:29AM
(#22747613)
To be fair sync feature is marked as unsafe to use in production in documentation.
Re:Prisma 2.0 Beta: Type-safe Database Access
by esistgut on Wednesday April 01, 2020 @09:59AM
(#22748504)
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.
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