Luca Steeb

This issue needs to either have some check in the engine startup and probably some general log reading from the engine which is streamed via jsonrpc, parsing it and then...

It's not possible right now. I have already raised this internally. In the meanwhile, you can declare an environment variable in the schema file and provide that directly or use...

Can you please describe where your `prisma.schema` and your env file is located?

Please share some more info, like your full dockerfile.

would be automatically fixed by #477

I assume your concern is instead of having fixed required parameters in Create instead of a single variadic parameter. The reason Create has this parameters is that we can enforce...

Only link and unlink (connect and disconnect), not nested updates and creates

Env support would happen in the Prisma CLI I believe, so I don't think changing anything in the Go client can solve this.

The example schema is gendered by Prisma introspection; with the field being lowercase and the relation attribute being uppercase. Sorry for the missing context, I thought I had added that...

@deanshelton913 Can you please elaborate? Are you using introspection with the Go client but run into this problem?