I tried to do the following

import { prisma } from '../../../prisma/prisma';

const mock = mockDeep<typeof prisma>();
jest.mock('../../../prisma/prisma', () => mock);

it('...', () => {
  mock.user.count.mockResolvedValue(2);
  fn()
})

and the function call does this:

const userCount = await prisma.user.count({ where: ... });

but im getting

undefined

for userCount instead of 2

any help would be appreciated!

😞 still havent been able to figure out

finally got it haha

Hey everyone! So for the last few weeks I’ve been designing and beginning to implement a GraphQL API using Prisma. I’m at a stage where I have enough of an API foundation to think about developing frontend. I’ll be using react-native and I have a few questions regarding fetching data from my API. I want to be able to provide users with an offline experience and therefore require cache. I also want to use subscriptions (real-time functionality in GraphQL). I’ve found Apollo Client and seen that it has a lot of good reviews, however, I’m not a huge fan of the built in React components that display the data. I haven’t used them so I can’t really be sure that I don’t like them, however I don’t think they’ll be great for query testing which isn’t a huge deal since I’ll be thoroughly testing my API and Prisma is tested. On the other hand I’ve used redux in the past and am wondering if it has the possibly of acting as a sort of cache when paired with simple https requests. Any thoughts are appreciated! 🙏

Hey, has anyone looked into getting https://www.elastic.co/apm to work with Prisma 2?

I didn't manage to find a good way that explains the setup of nexus (the framework) with prisma. I don't get where is the entrypoint, and get typescript errors with every t.model(it says that it doesn't have the .model part). Do someone have some tips for that?

Hi, I'm trying to implement managementApiSecret but I can't do it, I have an error : "Authentication token is invalid: 'Authorization' header not provided"

Where should I add the header ?

I have a prisma project which uses prisma 1.29. I need to update it to latest prisma 1. Threre is a breaking change on prima 1.31. I use prisma cli 1.34.10 to generate new data model files. can I directly update to latest prisma 1 or do I have to come step by step?

please help me migrate

when I trying to deploy it gives me this error. this userID field is something very critical

all the userID’s were gone after the forceDeploy

prisma working fine in my next.js app, just tried adding a background worker process (BullMQ) using the same codebase and prisma is now throwing an error about 'invalid findOne invocation' and then the exception has {"code": "ENOENT"}. but the same query works fine over in next.js land. any obvious ideas?

params look good, types of params look good, not sure what else to check to try to debug this

i assume the ENOENT means there's no connection?

if i log my prisma client in the env where it's working and the one where it's not the main difference appears in the 'engine' key of client object. working one has (port, platform, child, url) and broken one does not

feel like it has to be an issue from webpack doing something strange (missing files from node_modules or something, since they aren’t explicitly imported)? Anyone know of issues like this?

Hi, when using prisma client fetching data from mysql, i always got null for all fields, when I opened info, and found below error: “errors”: [ { “message”: “Invalid string length”, “locations”: [ { “line”: 2, “column”: 3 } ], “path”: [ “dashboard_config2" ],

my table definition is :

create table scm_dashboard.dashboard_config2
(
    `id`        varchar(255),
    `userId`    varchar(255) DEFAULT NULL,
    `vizState`  varchar(255) DEFAULT NULL,
    `changedAt` varchar(255) DEFAULT NULL,
    `createdAt` varchar(255) DEFAULT NULL,
    PRIMARY KEY (`id`)
)

where is the issue?

prisma.dashboard_config2.create works perfectly, the issue only happens to prisma.dashboard_config2.findMany

Hi, I've added PRISMA_MANAGEMENT_API_SECRET When I go on localhost:4466 it works, but not on localhost:4466/management, he says to me "Authentication token is invalid: Token can't be decoded: Invalid signature for this token or wrong algorithm." Yet I pass him the prisma token in the header...

How can I get the error that my server didn't start on my client?

in console.log

How would I filter using a "deep" property? For example, I have an

User

that has

posts: Post

How would I filter the list of users that has posted an specific post for example:

query GetUser {
  users (after: { posts_some: { title_eq: 'My post' } }) {
    name
  }
}

I'm using nexus and prisma2, and nexus is not allowing me to filter that deep with

t.crud.users()

Is it possible to have a generics-like/inheritance model attribution in the

schema.prisma

? Like:

model User {
  name   String
  email  String
}

model LegalPerson {
  @@inherit(User)

  socialNumber   String
}

model Company {
  @@inherit(User)

  address   Address
}

And then have nexus output something like

t.crud.Users()

?

Hey Community!