I have an application built on top of the nexus-prisma generated GraphQL API, served using Apollo. So far I have managed with the CRUD operations + some additional Queries. However, I want to add some server side logic to some of the mutations, that is, given certain data in a mutation, change something else or do something else (e.g send email). I don't find any good examples of this, although I assume making a custom resolver is the way to go about it.

Never mind, I see that a custom resolver is the easy way to go about it

Ok, similar, but different question. On a specific create Mutation, I want to add an input field that results in some additional stuff to be generated. It doesn't make entirely sense I think to add it to the object, since it is not a relevant field to read out later. How will I go about doing that? A custom write-only field so to speak.

ah, maybe prismaInputObjectType?

Hi, is there any way to transaction manually in prisma1? (not nested mutation)

Hi, I’m trying to figure out some performance issues with our application, and I’m seeing a huge variance in how long it’s taking to retrieve data. Sometimes querying a type will take 2 seconds, sometimes 0.02! Any ideas what we should be looking for?

I have a type Process that is exposed via GraphQL to react-admin, using @weakky/@Marc-Antoine dataprovider. I would then like to add parameters to update and create that are not stored in the database. I am able to update e.g. ProcessCreateInput to have the relevant fields such that they show up in the GraphQL schema, but the resource handling in ReactAdmin is based on just Process. This seems to cause the additional fields to be lost en route to the server. Is there some solution on the server side, or is this a limitation in the data provider perhaps?

Hello, we started getting these errors all of a sudden:

Uncaught Error: Directive "isAuthenticated" may not be used on FIELD_DEFINITION.

Directive "isAuthenticated" may not be used on FIELD_DEFINITION.

Directive "isAuthenticated" may not be used on FIELD_DEFINITION.

Directive "hasRole" may not be used on FIELD_DEFINITION.

Directive "isAuthenticated" may not be used on FIELD_DEFINITION.

what's going on?

Anyone seen this before or know what might be causing it? Is it something in our application or does prisma1 include caching or dataloading that might be causing this?

I haven't tried the prisma admin dashboard for a while on my local setup, but now I inexcplicably get what looks like GraphQL playground instead, although without any schemas to work with. Going to localhost:4466

Hmm, seems like I probably have a routing issue

It actually gives me the playground from my application (which normally lives at :4000)

So if I tack on /default/default/_admin I get there, but I'm a bit confused as I'm pretty sure I didn't need to do that in the past. Could there be some configuration that I have messed up?

Ok, so just opening up one of my collections (mongo database) in prisma admin, I get an error on a null value that shouldn't be there. The collection has 4 required fields though, so how do I figure out which one?

Hey everyone Is there a way to run the graphiql tool on my browser from an app deployed to heroku?

graphiql tool / graphql playground (the one that you can run locally by accessing localhost:4000)

Posted this in wrong channel, but it is about Prisma 1: Do anyone know of the arrayFilters usage in the prisma mongo driver? Our database in testing seems to be older than the introduction of that feature, causing issues. The curious bit is that I am pretty sure that this didn't happen prior to a schema update I had. I am sortof presuming that more array updates are now done since the schema update created more relational links (but the old version weren't free of it either ...)

How should i setup my project on a production environment to call the prisma deploy command after I have made changes locally on dev environment, but now after I push my code I need the server to be updated too? (https://v1.prisma.io/docs/1.34/prisma-cli-and-configuration/cli-command-reference/prisma-deploy-xcv9/) Would that be by adding something to the post deploy hooks on prisma.yaml file or manually ran on the server somehow (I'm using heroku)

I have a self refrencing relationship that i want to change from one-to-one to one-to-many.. Prisma tells me

! You already have nodes for this model. This change may result in data loss.

Why is this breaking? i.e. going from this:

type Node {
  parent: Node @relation(name: "NodeParentChildren", link: INLINE)
  chilldren: Node @relation(name: "NodeParentChildren")
}

To this:

type Node {
  parent: Node @relation(name: "NodeParentChildren", link: INLINE)
  chilldren: [Node!]! @relation(name: "NodeParentChildren")
}

Anyone currently doing application performance monitoring with Prisma 1? Have any suggestions of where we could start or tools we may not know about yet, or any experience you’ve had so far with certain tools?

Right now we have Heroku’s out of the box monitoring and that’s about it for knowing how long things are taking, but we are trying to figure out how to more granularly analyze and dig into which queries/mutations are taking the longest kinda thing.

anybody help me

I have a question

Is it possible to use pgbouncer with prisma1?

Hello. Currently, our company is using Prisma 1. Currently, our service is using ECS-based Prisma 1 by clustering 10 units. The CPU usage is higher than I thought, so even though I’m using the 4vCore 8Gb peak performance, I keep getting the error below.

[INFO] Fatal error during deployment worker initialization: akka.pattern.AskTimeoutException: Ask timed out on [Actor[<akka://single-server/user/$e#1930414073>]] after [300000 ms]. Sender[null] sent message of type "com.prisma.deploy.migration.migrator.DeploymentProtocol$Initialize$".
akka.pattern.AskTimeoutException: Ask timed out on [Actor[<akka://single-server/user/$e#1930414073>]] after [300000 ms]. Sender[null] sent message of type "com.prisma.deploy.migration.migrator.DeploymentProtocol$Initialize$".
	at akka.pattern.PromiseActorRef$.$anonfun$defaultOnTimeout$1(AskSupport.scala:596)
	at akka.pattern.PromiseActorRef$.$anonfun$apply$1(AskSupport.scala:606)
	at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:205)
	at scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:870)
	at scala.concurrent.BatchingExecutor.execute(BatchingExecutor.scala:109)
	at scala.concurrent.BatchingExecutor.execute$(BatchingExecutor.scala:103)
	at scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:868)
	at akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:328)
	at akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:279)
	at akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:283)
	at akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:235)
	at java.lang.Thread.run(Thread.java:748)

It turns out that EKS works much more reliably to cluster than ECS, so we are building a new one EKS, but similar errors occur. I wonder if the database is twisted, but I don’t know how to fix it. Can anyone help? Using Prisma 2 would be ideal, but as redevelopment is going on soon, I can’t change much. Thank you.

Hey hi guys, how I can search a value in a collection using prisma and MongoDB?

Hello, I was deploying a prisma 1.13 project when I suddenly redirected to a prisma page for auth, I authed with github(not sure if that account actually is connected to prisma), and then received this error:

ERROR: Variable "$input" got invalid value {"workspaceSlug":null,"clusterName":"default","serviceName":"default","stageName":"default"}; Expected non-nullable type String! not to be null at value.workspaceSlug.

{
  "errors": [
    {
      "message": "Variable \"$input\" got invalid value {\"workspaceSlug\":null,\"clusterName\":\"default\",\"serviceName\":\"default\",\"stageName\":\"default\"}; Expected non-nullable type String! not to be null at value.workspaceSlug.",
      "locations": [
        {
          "line": 2,
          "column": 17
        }
      ],
      "code": 222
    }
  ],
  "status": 400
}

any help?

The above issue was solved when I matched cli version to server's, 1.13 but now I get 403 FORBIDDEN

ERROR: GraphQL Error (Code: 403)

{
  "error": "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n</body>\r\n</html>\r\n",
  "status": 403
}

although I'm using the same managementApSecret we use for production!

I have solved the above as well, the request was getting blocked for a size constraint. Now the

graphql get-schema --project database

command is not getting the updated schema, and since we use an old version of prisma, then prisma generate is not available to use. Any workarounds for this?

SOLVED! how? I created a new type:

type Lol {
name: String
}

ran deploy then get schema then removed Lol type then deploy !