Luca Steeb

Thanks for the elaborate description. I don't think there is a better way to do it right now. Glad to hear that you at least found a workaround 😅 Are...

Sorry for the late response. Can you please provide your full schema? It seems to be related to code generation and that seems to be related to your schema.

I'll re-open this as it's still a bug that should be fixed. Thanks for the helpful info though!

@PetkoPetkov03 Can you please share the config part of your prisma schema and the commands you are running?

They are not necessarily needed, you're right. However, I think it's more logical to use a function call for two reasons: 1) It looks more like an action. It's not...

It's planned for the long, but not right now as this takes a lot of effort to properly implement and maintain, as it also needs work not just on the...

Basically the OrgIDEntityID() unique function call is now allowed internally in the QE, so it's a bug in the sense that the Go client allows this. We may not add...

I think you would need to pass additional parameters in .Link, the operation In just does not work in this case (it is actually a bug that this syntax does...

An open question: The current signature for optional fields is `(v, ok)`. What should we do about that? Return an error `ErrNull`?

I want to prevent the case of returning `nil` every time even though the user didn't fetch for it. Although I see your point.