Multiple prisma clients - many databases

In code

export function getPrismaFromContext(context: any) {
  const prismaClient = context.prisma;
  if (!prismaClient) {
    throw new Error("Unable to find Prisma Client in GraphQL context. Please provide it under the `context.prisma` key.");
  }
  return prismaClient;
}

there is a fixed “prisma” key, but If we would add parametrization of this name in the config, then we would be able to use it with many databases that have their own clients in context.

Probably we need extend this cod by new option with default value “prisma”:

export interface ExternalGeneratorOptions {
  emitDMMF?: boolean;
  emitTranspiledCode?: boolean;
  simpleResolvers?: boolean;
  useOriginalMapping?: boolean;
  useUncheckedScalarInputs?: boolean;
  emitIdAsIDType?: boolean;
  emitOnly?: EmitBlockKind[];
  customPrismaImportPath?: string;
}

then add this param to function generateHelpersFile and replace “prisma” by this parameter in

    export function getPrismaFromContext(context: any) {
      const prismaClient = context.prisma;
      if (!prismaClient) {
        throw new Error("Unable to find Prisma Client in GraphQL context. Please provide it under the `context.prisma` key.");
      }
      return prismaClient;
    }

[viis233]

I modified the generator and it seems to be working fine. I don’t know if there is a hidden problem.

[MichalLytek]

Conflict between declared prisma context key and runtime prisma clients in graphql context