Upgrade Prisma past 5.1 after nested write regression is fixed
Closed this issue · 0 comments
I'll make a note about what's happened in my upcoming PR, but in short, has decided to add to "reasons I wish we hadn't chosen Prisma" pile by introducing a regression in 5.2 that breaks for anyone using nested writes (e.g. create: { foo: { create: { bar: { ... } } } }
). I have absolutely no idea what's going on with Prisma at the moment, they seem to be making barely changes to the actual ORM in the last 6 months and haven't addressed a huge regression in few several months, perhaps their entire team been moved over to their serverless/cloud crap.
Regression is being tracked here prisma/prisma#21182, will get us onto latest once resolved. Though at this point I've pretty much given up hope on Prisma actually adding any of the features we've been waiting for (e.g. bitwise operators, nested createManys) in the future. Seems pretty likely their cloud crap won't go anywhere and VC money will dry up in next few years. Gahhhh!