Shawn Jones

> For further information, I upgraded to 0.27.0 and this issue does not exist in that version. double-checking, you don't have this problem with `0.27.0`? we do have this problem...

same with the other `ServicePointManager` stuff https://github.com/snowflakedb/snowflake-connector-net/blob/21f2d01a2add057ed5d19130d9a485b7289f5ff8/Snowflake.Data/Core/HttpUtil.cs#L38-L40

related to this? https://github.com/prisma/prisma/issues/20619

> You need this field in inputs in order to properly find unique records in db via graphql api. sorry, my example should have marked the `id` as `@unique` as...

to make this more clear, i can hide regular `@unique`s but not `@@unique`s -- as long as i leave at least one of the regular `@unique`s available to the caller...

@MichalLytek -- here's a clearer example: ``` model MyModel { id String @unique /// @TypeGraphQL.omit(output: true, input: true) organizationId String @@unique([id, organizationId]) } ``` this currently generates: ``` export declare...

@MichalLytek see clarification above

He’s saying that’s what I’d need to add if submitting a PR. I do plan to make such a PR in the next few weeks.