fix(raw queries): correct None handling for all fields

[AstreaTSS]

Change Summary

See #998 for the most part.

This PR goes in and makes the check mentioned in the above issue happen earlier.

Checklist

• Unit tests for the changes exist
• Tests pass without significant drop in coverage
• Documentation reflects changes where applicable
• Test snapshots have been updated if applicable

Note

Adding tests for JSON was not done due to technical difficulties I had when testing. Apparently, optional JSON fields can't accept a None value when being created, according to Prisma, despite the fact that I see it as optional in the schema used. I'll leave what errors I got below, though it may be just a me thing.

record = await client.types.create({'json_obj': None})

prisma.errors.MissingRequiredValueError: Unable to match input value to any allowed input type for the field. Parse errors: [Unable to match input value to any allowed input type for the field. Parse errors: [`data.json_obj`: A value is required but not set, `data.json_obj`: A value is required but not set], Unable to match input value to any allowed input type for the field. Parse errors: [`data.json_obj`: A value is required but not set, `data.json_obj`: A value is required but not set]]

Agreement

By submitting this pull request, I confirm that you can use, modify, copy and redistribute this contribution, under the terms of your choice.

[RobertCraigie]

Adding tests for JSON was not done due to technical difficulties I had when testing

ah I think this is because of #714

[RobertCraigie]

Thanks so much for the PR! Sorry for the regression in the last release.

I pushed a commit adding tests for the synchronous client