Thanks for reaching out. We have not yet tested Prisma with PGAdapter, so we can't make any statements on how well/bad it will work with Prisma.

This specific issue however is a PGAdapter problem. The SET NAMES 'UTF8' syntax is not a standard PostgreSQL statement, but it is something that PostgreSQL apparently has added support for to adhere to the ANSI SQL standard. See https://www.postgresql.org/docs/current/multibyte.html. PGAdapter currently does not take that possibility into account.

Thanks for the response.

I wasn't aware of this and had wrongly assumed that Prisma may have been accidentally sending mysql commands based on some quick google searches.

I noticed this project doesn't accept pull requests. Could I submit compatibility with Prisma as a feature request?

I noticed this project doesn't accept pull requests.

Hmm.... Maybe it's time to update that part of the documentation. Let me check with a couple of other people as well.

Could I submit compatibility with Prisma as a feature request?

Certainly!

Certainly!

Would love to see a popular type-safe typescript ORM get Spanner compatibility!

FYI, I tried SET NAMES 'UTF8' in both the DDL and Query editors and both returned an error. I'm not sure if this is because the spanner console runs a PGAdapter in the background which fails for the same reason.

DDL Editor:

QUERY Editor:

Hey, Prisma here 👋

Amazing to see this issue, and how @NOT-HAL9000 is pushing forward to figure out what is standing in the way of Prisma and Google Cloud Spanner (via PgAdapter) to work together (they mentioned it in our issue prisma/prisma#717 (comment)).

Might it be as simple as accepting SET NAME 'UTF8' in the adapter and swallowing it instead of forwarding it (for now)?

As we are currently basically just trying to find the real blockers down the line (which probably will be other, not supported queries), if someone (*hint @NOT-HAL9000 *hint 😆) opens a PR is there a simple way to test that code/adapter locally?

@NOT-HAL9000 I've created #589 for the more generic request to add support for Prisma, so we can treat this issue as a specific issue with the set names ... statement.