Luca Steeb

However, then I think you might argue that instead of returning an error, we might just a nil pointer for required fields instead of erroring? The advantage of that being...

@johnpena What do you think about my previous message?

@darmie Can you please open a new issue? Thanks!

Returning detailed errors such as: ```go type UniqueConstraintViolation struct { Message string Fields []string } type (e UniqueConstraintViolation) Error() string { return e.Message } ``` is unfortunately not as simple...

depends on https://github.com/prisma/prisma/issues/5040

@mavilein This is how it works. However, it may not be clear what should go into FindOne, since the argument is an interface. For example, the argument in FindOne may...

This would be a breaking change which everyone would need to adapt. I'm not sure if it's worth adding the new methods first and only deprecating the old methods.

This is really just for the Prisma CLI which is packed into the Go client – so unfortunately not related to Go. This issue probably belongs somewhere else 😅

/rebase

/rebase