and every one of the frontend applications has this custom resolver that is supposed to do stuff even if there is no client connected and using the subscription

ofc, it’s gonna be the app replica that handles the mutation request via the graph. nvm

photon related question

Setup ————————— Prisma2 - preview13.3 Mysql 5.7 Nexus Schema: ————————— model ProfileInfo { id String @default(cuid()) @id @unique createdAt DateTime @default(now()) updatedAt DateTime @updatedAt title String language String categories String? description String owner User? } model User { id String @default(cuid()) @id @unique createdAt DateTime @default(now()) updatedAt DateTime @updatedAt email String @unique password String fullName String profile ProfileInfo } Mutation : —————————— t.field(“updateProfileInfo”, { type: “ProfileInfo”, nullable: false, args: { profileInfo: InputProfileInfo, ownerId: idArg() }, resolve: (parent, { profileInfo, ownerId }, ctx) => { return ctx.photon.profileInfos.create({ data: { ...profileInfo, owner: { connect: { id: ownerId } } } }); } }); Question : —————————— When I execute Mutation from Playground, Owner is always null. Even though the database has entry in owner column. Note: Same setup works for SQLlight.

what can I have done wrong when I can’t get any data from my DB when using prisma mySQL on the backend and react and apollo Client on the front end?

Just updated to react-relay 6.0.0 and I have a weird bug: no requests are being made, like if relay wasn’t connected to the server. Rolled back to 5.0 and everything works. Anybody aware of any breaking change? (nothing related in release notes it seems)

hi everyone

recently I have deployed prisma to dokku

just like the tutorial link

but some after the 1st deploy

I cannot access to the app

when I checked the logs

it showed

Could anyone help me out 😞

https://stackoverflow.com/questions/58315585/variable-data-expected-value-of-type-votecreateinput?noredirect=1#comment103030944_58315585 can anyone help me out?

datamodel.prisma: I want to create a datamodel that has

account_id:Int!

as being the unique “key” and to dispense with `id:ID! @id`However when I use `@id`on the above I do not have access to this in the mutation from the playground. How can I set this up so I can enter data that will be unique (account_ID will be 101, 102, 103 etc) but that will be seen as the id of the datamodel.

I had to sum all my transactions in my prisma1 to to create some logic. Unfortunately, the query return only 1000 rows. (I have 35'000 transactions). I create a second sql server with a sql query to return the value. Is it a good practice? What other workaround should I do to solve this issue?

anyone knows about

wait a sec

wtf?

error is gone?

sorry

Currently i’m trying the prisma 1.34 get started steps. By step “build an app” i’m running against a wall with: “TypeError: nexus_prisma_2.prismaObjectType is not a function” in step 4 … npm run dev … anyone can help? https://www.prisma.io/docs/get-started/03-build-graphql-servers-with-prisma-TYPESCRIPT-t201/#implement-graphql-api-based-on-crud-building-blocks

I am trying to deploy Prisma on Docker in Windows Server 2016, but I get this message:

1.34: Pulling from prismagraphql/prisma
ERROR: image operating system "linux" cannot be used on this platform

Any ideas on how I can configure Docker on WS to support the Prisma image?

hey guys, this is more of a nexus related question but is it possible to extends an interface with another interface? Let's say I have a Book interface and a Node interface. Can I extend the Book interface with the Node interface so I don't have to specify id separately on the resolve types of Book?

it Looks like, that the automated Generation step of Prisma doesn't support an explicitly set .yml file i added a -p with a different filename than Prisma.yml to my deploy statement but when it should generate the Clients for me, it says, it cannot find the Prisma.yml file, if i start generate manually everything works fine

Guys, are there any rumors regarding the release date / Prisma team progress so far? 🙂

anyone have an idea with graphql-shield

isAuthenticated: rule()((parent, args, context) => {
    const {
      app: {
        user: { id }
      }
    } = context;
    return Boolean(id);
  }),

not sure why i alway got error with not authorized even the token was correct.