findOne: Stop throwing an error when no record found

[schickling]

Even though we're currently working on some bigger API changes which will fix this behavior, it will take a little while until all these changes will be implemented and ship. In the meanwhile I'd like to address one of the most frequent points of feedback by Prisma 2 testers which is to stop throwing an error when no record was found when using the findOne operation. (See #89)

@timsuchanek would be great if you could address this during the current sprint 🙏

[danlannz]

@timsuchanek @schickling was this reverted in Preview 16? I'm getting the following error in my seed script but Preview 15 works as expected

  106 for (const [modelName, models] of Object.entries(data)) {
  107   for (const entity of models) {
  108     const existingEntity = await (photon as any)[modelName]
→ 109       .findOne(

Reason: Error occurred during query execution:
ConnectorError(RecordDoesNotExist)

[yovanoc]

Yes same for me, regression I supposed :/

[pantharshit00]

I can confirm this regression.

[pantharshit00]

[pantharshit00]

Closing in favour of prisma/prisma#914 which we are using to track the regression in our milestone

[tvvignesh]

Still facing similar issue. Added details here: prisma/prisma#914 (comment)