Why?

Databases (like Postgres) do support JSON columns and provide a set of options to manipulate content within these (e.g. filtering on nested properties...).

Prisma currently supports basic querying capabilities on JSON fields, which hinders developers making use of these fields in their applications from using what the database natively offers. This requires to implement runtime workarounds which are inefficient and time consuming.

Sub-problems