maybe this is not possible?

I prob won’t be able to help you, but FYI without any examples you can’t really expect anyone to know what you’re attempting to do. I suggest you provide an example of some code you wrote, like your resolver. Or even better a stripped down example repo with everything in place showing the issue you have.

I did above last night

ah I see, only seen your messages today

yes

prisma client doesn’t forward queries

yeah I posted snippets of my data mode, query, resolvers, and log output last night

I had the same issue over the last few days

what did you do ?

so you can pass the info object

what does passing the info object do?

its not really documented well to be honest

it’s frustrating

yeah I considered AWS app sync, but I’m migrating to an existing graphcool app. Migrating to app sync could end up taking longer

this is just for a side project for me

yeah 1.7 docs do make it a bit confusing with the new prisma client

I wish there was an interactive console

prisma-binding is the lib that forwards info btw

what version of prisma is that associated with?

its not deprecated, it’s meant to coexist

but doesnt 1.17 mean you need to use prisma-client ?

no

its not going to be deprecated?

heres an example of how I use both atm:

const { Prisma } = require("prisma-binding");

const { prisma } = require("../prisma/prisma-client");

const db = new Prisma({
  typeDefs: "prisma/graphql-schema/prisma.graphql",
  endpoint: "<http://prisma:4466/api/dev>",
  secret: "abcd1234"
});


const server = new GraphQLServer({
  typeDefs: "src/schema.graphql",
  resolvers,
  context: req => ({
    ...req,
    prisma,
    db
  }),
  formatError: error => {
    console.log(error);
    return error;
  },
  formatResponse: response => {
    console.log(response);
    return response;
  }
});

thank you!

np

so if you need to use

prisma generate

for prisma client

you can have multiple generators in the prisma.yml:

datamodel: ./prisma/datamodel.graphql
endpoint: <http://prisma:4466/api/dev>
secret: abcd1234
generate:
  - generator: javascript-client
    output: ./prisma/prisma-client/
  - generator: graphql-schema
    output: ./prisma/graphql-schema/

oh man

no worries

this is so confusing

lol yeah at first

This is a blog post about the info object if you want to know some more informations about it... https://www.prisma.io/blog/graphql-server-basics-demystifying-the-info-argument-in-graphql-resolvers-6f26249f613a/

@Luke this might be interesting for you regarding the client vs bindings discussion: https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394/17?u=nikolas

@nikolasburk Thank you!!!

FYI, we've also a section to the "Common resolver patterns" guide about this topic here: https://www.prisma.io/tutorials/a-guide-to-common-resolver-patterns-ct08/#scenario:-implementing-relations-with-prisma-client