Is it intentional that things like

AND

&

OR

on the

[Type]WhereInput

doesn't exist for findUnique() - but it does for findFirst()? I'm sitting with a specific usecase where I'd like to avoid using findFirst, because findUnique is perfect for the use case. It really doesn't matter, just curious as to why exactly it isn't universally added.

findUnique uses only unique fields to find a property, this will have performance benefits over large data sets and is it strict in using indexed properties. findFirst is essentially findMany with a take of one and returns the 0 index of the array. It was created to solve people having to return findMany()[0] and writing their own catches and checks