Prisma

changed some variable ordering and naming but I think it's the deploy

Most likely there is a `prisma generate` hook in your `prisma.yml` and prisam deploy regenerated the client for you?

Just to confirm, you are using Prisma client right?

You mentioned "Prisma binding" once and "Prisma binding client" once

But Prisma client and Prisma binding are separate products and `executeRaw` is exclusively a feature of Prisma client.

Happy that this got resolved for you though but I would love to work with you and understand what went wrong :slightly_smiling_face:

Feel free to DM me :slightly_smiling_face:

The prisma-bindings exposes executeRaw en the client does not

The prisma binding also exposes executeRaw

<https://github.com/prisma/prisma-binding/issues/262#issuecomment-441117971>

Prisma client exposes `executeRaw` and `prisma-binding` does so as well, according to this issue: <https://github.com/prisma/prisma-binding/issues/262#issuecomment-441117971>

I will validate this with a small repo and get back.

I just checked, I use executeRaw on bindings

Now which one is better :stuck_out_tongue:

Yes, apparently, they both expose `executeRaw`, I was incorrect about `prisma-binding` not exposing `executeRaw`.

So what one is better do you think? :stuck_out_tongue:

Client IMO, lower learning curve, auto-completion, more languages (Go, JS, TS, Flow) and types support if you are using a typed language.

<https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394>

This forum post would help you understand the differences, please feel free to ask further questions :slightly_smiling_face:

Thanks allot :slightly_smiling_face: loving this next level ORM by the way :slightly_smiling_face:

It has some things to improve on but it's already a joy to use

Sure, feel free to send your feedback via Github issues or here in slack. We would love to work with you and make this the best way to access data sources :slightly_smiling_face:

it was indeed the prisma.yml. It generated the schema and that made it break

Do you think that any key information in documentation would have helped avoiding this confusion? 