MongoDB deleteMany seems to send 2 identical read queries first before triggering the actual delete

[janpio]

As seen in #15084, a MongoDB deleteMany seems to send 2 identical read queries first before triggering the actual delete. One of those is probably not necessary:

$ ts-node ./script.ts
deleteMany
prisma:query db.User.aggregate([ { $match: { $expr: { }, }, }, { $project: { _id: 1, }, }, ])
prisma:query db.User.aggregate([ { $match: { $expr: { }, }, }, { $project: { _id: 1, }, }, ])
prisma:query db.User.deleteMany({ _id: { $in: [ ObjectId("6d795f757365725f69643030"), ], }, })

---

4.3.0-dev.84

[Jolg42]

Can reproduce the 2 identical queries

deleteMany
prisma:query db.User.aggregate([ { $match: { $expr: { }, }, }, { $project: { _id: 1, }, }, ])
prisma:query db.User.aggregate([ { $match: { $expr: { }, }, }, { $project: { _id: 1, }, }, ])
prisma:query db.User.deleteMany({ _id: { $in: [ ObjectId("6d795f757365725f69643030"), ], }, })
...

Note: I only see db.User.deleteMany line on a second run