Currently, if Prisma/DB is unable to parse a statement (due to a wrong or unsupported syntax), it will forward the query to the database directly. This is because we do not have support of the full SQL language yet. Therefore, the error thrown is by the database itself, which does not recognize the ENCRYPTED keyword.

That said, better error messages are in the pipeline, so cases like this will be less confusing to the user.

if Prisma/DB is unable to parse a statement (due to a wrong or unsupported syntax), it will forward the query to the database directly

@cheziyi I think Prisma/DB no longer does this?

if Prisma/DB is unable to parse a statement (due to a wrong or unsupported syntax), it will forward the query to the database directly

@cheziyi I think Prisma/DB no longer does this?

It does, as long as it can't be parsed.

Are you sure? My understanding was that whatever can't be parsed errors out, and if you need to send through you can do PRISMADB BYPASS ...

Are you sure? My understanding was that whatever can't be parsed errors out, and if you need to send through you can do PRISMADB BYPASS ...

Yup, queries that can't be parsed are sent to the database directly to attempt to have as much support for DB clients as possible. PRISMADB BYPASS is meant for queries that can be parsed, but we do not want to execute at the proxy. It will still work for queries that can't be parsed.