Prisma handles values based on core types and best effort implementation as mentioned in this spec: https://github.com/prisma/specs/tree/master/schema#data-types

However, many databases support custom data types like JSON, timestamp without time zone, date, binary formats etc.

Prisma should provide a mechanism to utilize these DB specific primitives.

Related issues:

• Custom Long type Unexpected token. when running prisma2 lift save after adding custom type definition migrate#94
• DateTime scalar Support a Date Scalar Type  #255
• JSON/JSONB types Support for JSON/JSONB prisma-client-js#60
• Postgres timestampz mismatch between the DateTime types of Prisma and the ones of Postgres (timestamptz unsupported) #552
• Query Postgres Table with UUID as ID raises error Query Postgres Table with UUID as ID raises error #479

Possibly related:

• Using Prisma enums results in setting DB-level default value #741

Spec issue prisma/specs#119