anyone have an issue with

graphql-yoga

and

nodemon

where when you make a change in development inside one of the resolver functions, it doesn't get picked up unless I kill

nodemon

completely? but what is weird is changes outside the functions, do get picked up immediately

hey, I am trying to get prisma to work, but after I install it through NPM and run the cmd prisma I get 'MODULE_NOT_FOUND': Cannot find module 'ps-node' and the picture has the more detailed error report. Is there anyone that knows how to fix this?

hi, I am trying to set up prisma on ubuntu connected to an existing postgres db. when I try to run docker-compose up -d I get an error saying no pg_hba.conf entry for user "test" database "postgres". I understand that this would give an error because my pg_hba.conf is configured to only accept user "test" for database "test". however in my docker-compose.yml the database name is specified as "test" and not "postgres". any ideas why it is trying to connect to a database named "postgres" instead of "test" ?

If I am passing an ID of a type to a different type and storing it as a value on one of its fields through the front end- is there a way to create a relationship in the backend between these two types? Or is it not possible because I am passing the The id from the front end

Heads up at that Graphcool is a victim of this attack: https://github.com/dominictarr/event-stream/issues/116

That said it doesnt seem to be relevant except for a very specific combination of packages (targeting some BTC wallet), but might be good to be aware of. The package has been removed from npm so people's builds might start failing 🙂

I’m having an issue understanding why I can’t directly import the generated graphql mutations, queries, and types into my graphql-yoga server

Anyone?

What should go in here?

Yeah what's the point of Prisma if yoga can't use the queries/mutations generated by Prisma? Or can it? Is there a benefit over using yoga with say, Sequelize?

hi all

i’m getting start with go. after run dep init and dep ensure. then i run go run index.go i got error

# sandbox/hello-prisma/generated/prisma-client
generated/prisma-client/prisma.go:22:15: undefined: Exists
generated/prisma-client/prisma.go:48:14: undefined: Client
generated/prisma-client/prisma.go:1420:9: undefined: Client
generated/prisma-client/prisma.go:1421:11: undefined: Instruction

Anyone please help me?

Any ideas how I can resolve cors issue?

is building a passthrough graphQL layer on top of an existing API (using resolvers, etc) something I should do with Prisma or fall back to GraphCool?

Hello folks ! Are there known issues with server-side subscriptions ? I can’t make it work, nothing is triggered. In particular, is the subscription query calling prisma or the app api ?

Is there a way to rename a named relations? e.g. original:

type User {
  id: ID! @unique
  name: String!
  posts: [Post!]! @relation(name: "UserOnPost")
}

type Post {
  id: ID! @unique
  title: String!
  user: User! @relation(name: "UserOnPost")
}

changed datamodel:

type User {
  id: ID! @unique
  name: String!
  posts: [Post!]! @relation(name: "PenisOnPost")
}

type Post {
  id: ID! @unique
  title: String!
  user: User! @relation(name: "PenisOnPost")
}

I keep getting

✖ You are creating a required relation, but there are already nodes that would violate that constraint.

when

prisma deploy

Does anyone else have a problem with Prisma being slow today?

Hi! Does any one know whether we can set an

onDelete

for

pgRelation

?

I don’t understand why my server side subscription does not work... Here is my subscription :

subscription {
  chapter(where: { mutation_in: [UPDATED] }) {
    mutation
    updatedFields
    node {
      id
      title
    }
    previousValues {
      id
      title
    }
  }
}

And prisma.yml :

subscriptions:
  chapter:
    query: ./chapter.graphql
    webhook: <https://XXXXXXX.execute-api.eu-west-1.amazonaws.com/dev/prismaSubscriptions>

A test query :

mutation {
  updateChapter(
    where: {
      id: "cjot5ky4d521f0a75pytaabzl"
    }
    data: {
      title: "Hello 2"
    }
  ) {
  	id
  }
}

The webhook is a node lambda, I see cloudwatch logs when visiting the url manually. Calling the query in playground returns the result, but no logs show up in the lambda cloudwatch logs. Any idea ? 🙂

hello guys, after i add management key, my node unable to connect to prisma, what am i missing?

Of course ! I needed a POST method, not a GET method...

Hello guys ! Has anyone had a problem with deeply nested selector on queries ? Given the entities A, B and C, with A -> B and B -> C, I am trying to query :

{ 
  A {
     B {
         C ( where : { field_not: null } ) {
             id
        }
    }
}

Is giving me an error :

Unknown argument 'where' on field 'C'

Hey Friends, I have a couple of beginner-ish questions and I wonder if anyone here can point me in the right direction... 1) I'm looking to set up a cron job that runs a function that will check the database and send out various reminders to users based on certain criteria. I'm at a little bit of a loss as to where to start with this in a prisma / gql-yoga environment. 2) I'm noticing that my application is at times very slow and I'm wondering if this is simply because I'm using the free Prisma dev environment. Is the paid tier faster or is it likely that the issue is on my end? Thanks in advance for any help

hello, I have a question related to open source licensing. could someone tell me what type of license Prisma has?

Anyone having trouble on search in prisma console? I get the following error:

"message": "Argument 'where' expected type 'ProjectWhereInput' but got {OR: [{id_contains: \"test\"}, ....

How can I remove or add an item to a field with update operation?

I just migrated my codebase from prisma-binding to the new prisma-client. I’m noticing a significant slowdown in my app, 4-5 seconds to load the home page vs 1-2 seconds before. Rolling back the commit will undo the problem. Has anyone else encountered this?

It seems that search on prisma console search breaks when you have a field of type

[String!]!

in your datamodel.

Hello guys, I was wondering how do I use schema delegation as before in Prisma 1.21?