@hamdi

sorry too tempting

same tbh

and wtf, mongoose? this is Prisma slack lmao

working on relay mutation updater function: how do I update relay store data that has nothing to do with the mutation response I want to update my UI that was loaded via Relay fragment — before the mutation happened — using the mutation payload.(edited)

Anyone here migrate from Graphcool to Prisma? I got my Prisma server up and running but already have clients deployed to production using the old Graphcool server. Any way to easily backport certain schemas into Prisma? For example:

allUsers

->

users

or

updateUser(*stuff*)

->

updateUser(data: *stuff*)

I am consistently getting

FATAL: too many connections for role

on my prisma server. Is there a way set the max number of connections prisma will use?

I am a bit confused... Firstly, I did get here through Scaphold.io site, which, it seems, has no connection to Prisma. Secondly, I don't understand why Scaphold.io is still working since they emailed everyone about shutting down in may. Anyone with some insights?

Hello, I’ve written here the issues I am facing when trying to deploy to Heroku https://github.com/dpetrick/prisma-heroku/issues/1 . I would really appreciate it if anyone can help.

I’m using graphcool instead of prism and i want to sort my data (e.g. Items which have coordinates saved in the db) with a query based on a dynamic value/params like coordinates of the user. The approach i’m thinking of is extending Query

extend type Query {
   allItemsWithDistance(lat: Float, lng: Float): ItemPayload
}

will this work with subscription?

If I want to make a Feed component, and have a simple toggle for Live Feed (Subscription). So they cant choose if to use Subscription or not. What would be best practice?

name

in the filter is not of the String type but of an enum type. Any idea how I can specify the enum value as the value of

name

.

const userRole = await context.db.query.role({
        where: {
          name: 'USER'
        }
      }, `{ id }`)

FYI: This is the structure of the enum:

enum AvailableRoles {
  USER
  AUTHOR
  EDITOR
  ADMIN
}

would it be right to say that running graphcool would be easier

as u dont have to bother about resolvers

the forum post differentiating the two says that prism is easier to develop with, and yet you can run graphcool in docker

all the other issues I don't care about

Had anyone used fragments in prisma requests and got a luck? Can anyone help with this? Stuck for a long time I've tried to use

addFragmentToInfo

but it doesn't seem to be working 😞 https://github.com/graphql-binding/graphql-binding/issues/116

oh well prisma with serverless it is

And

request

doesn't work 😞 https://github.com/prismagraphql/prisma-binding/issues/182 @nilan @nikolasburk please, take a look at this and 116 issue. It seems to just impossible to use fragments over

prisma-binding

. A huge stopper 😞

and another one..... https://github.com/prismagraphql/graphql-request/issues/86

can anyone point me to a resource on how one might implement an email verification route in yoga?

Can someone point me to a resource on how to make group with members in them, that have different permissions? thx

Does anyone have an example of resolving queries on nested types with graphql-yoga? (not using prisma for this one, just wrapping a REST API)

Has anybody got experience with running a

ws

websocket server (not GraphQL subscriptions but rather a pure websocket server) in combination with graphql-yoga? Posted some details in #graphql-yoga

so I have a user type:

type User {
  id: ID! @unique
  email: String! @unique
  password: String!
  name: String!
  posts: [Post!]!
  role: Role! @default(value: "EMPLOYEE")
  active: Boolean! @default(value: "false")
  token: ActivateToken
}

type ActivateToken {
  id: ID! @unique
  user: User!
  token: String! @unique
}

but when I am in my yoga server

const user = await ctx.db.query.user({ where: { id: args.userId } })

doesn’t return the associated token type

am I missing something there

everything is present in the database

and when I run the query on the prisma server I can get the token

Hey people, just wanted to share my enthusiasm in using GraphQL Voyager to visualize both the GraphQL Server API and the Prisma Server APIs by just `yarn add graphql-voyager -D`'ing and then adding it as a middleware in your server init like

server.express.use('/voyager', voyagerMiddleware({ endpointUrl: '___GRAPHQLSERVER_OR_PRISMA_ENDPOINT___' }))

(note: use

'/'

as the endpoint if you are targeting your server) I'm a visual type of learner and this has helped to design my schemas in a much more intuitive way Also, here's the repo https://github.com/APIs-guru/graphql-voyager