That is what I see

So I updated this morning and all of my code using

$delegate

is broken, how are we supposed to load relations in queries now?

I believe delegations have been removed from prisma client

and you are expected to use prisma-bindings if you need to use schema delegation

From what I’m seeing it looks like that is indeed the case, what is the intended replacement?

Isn’t prisma-client the replacing to bindings? I’m supposed to have both in my project now?

I guess so. I found this out when pointing out an issue in the documentation

It seems the team is working on documenting the migration path. There’s an open issue discussing this: https://github.com/prisma/prisma/issues/3104 Please consider chiming in to make the conversation more public

so much confusion around prisma client/binding 🙂

hey I am getting

code: 3016 message: "Project not found: 'default$default'"

after deploying to DO

when trying to access

/

listProjects

returns 1 project as "prisma, staging"

I guess the deploy got the names wrong but how can I change that

is it possible to pull in a remote schema, but also defined resolvers in your own api before passing the query to the remote graphql service?

Hi all! Can anybody help me with a concurrency issue? 🙏 I want to update a node only if its

status

field value is compatible. How can I ensure that? The only way I found is to use

updateMany

(even to update a single entity) with a constraint on

status

value. It works great but batch updates don't trigger subscriptions 😞

Has anyone managed to paginate nested subfields with Prisma Client ?

Hi, someone has any example about webpack and workbox with background sync? Thanks 😁

what is my mistake

My logs

I’m trying to populate graphql Playground IDE with the query and the variables by using a browser URL link like so… http://localhost:4000/graphql?query=query+Greeting($name:%20String){greeting(name:%20$name){name}}&variables={%22name%22:%22Corey%22} The query portion works fine, but the variables won’t populate. Am I missing something? 🤔 This works fine in Graphiql.

Hey, guys. How do we return relations in the new prisma-client? It seems the

prisma.posts()

command will omit the

author: User!

field since it's a relation. Do I have to write my own fragment or another graphql query to send via

prisma.request

? This seems a little redudant, and I want to use what

prisma

has already generated.

Hey guys ... I'm busy looking at the possibility to convert an existing ReST API to Prisma. It seems that most of the services can be migrated over with not too much hassle. I do have question about the following features though: (1) Permissions: Is there solution for ACL/RBAC? CUrrently I have a few tables with roles and permissions, and the API builds an ACL list that gets passed to the client (use to protect certain client-side routes, show/hide some features, etc)? (2) Audit Trail: At the moment I log all actions (PUT/POST/DELETE) in an audit table. Is there a built-in auditing module in Prisma? (3) Event Sourcing: Anyone implementing event sourcing with a Prisma?

Hey everyone, is the integration with neo4j anywhere on the near timeline? And how can we help

Hello

I'm testing the beta with the generated javascript client

Is there a new strategy to leverage type safety when importing schema types when defining our own schema?

Like avoiding graphql-imports with comment lines but using something like graphql-tag?

@schickling Maybe you have an opinion about this 🙂