Stalled data, global usage of http-link-loader and facebook data loader about prisma-binding HOT 5 CLOSED

Not really, you could create a new prisma-binding instance for the second request, which will contain a new instance of the http-link-dataloader (with empty cache), instead of using the prisma instance passed in the request.

// instead of this
ctx.db.query.posts({...})
// this
getPrismaLink().query.posts({...})

// create a new prisma binding instance on demand
export const getPrismaLink = (debug: boolean = false) => new Prisma({
  endpoint: requiredEnvVars.PRISMA_ENDPOINT
  secret: requiredEnvVars.PRISMA_SECRET, 
  debug: debug 
})

from prisma-binding.

Was a problem with http-link-dataloader indeed.

from prisma-binding.

@nickluger do you have a solution for this issue? I've been tracking over here: prisma-labs/http-link-dataloader#3

from prisma-binding.

thanks! I'm going to give this a shot.

from prisma-binding.

@nickluger I can confirm that this solution works.

from prisma-binding.