I was using the options when declaring the server

but you have to do it when starting the server

damn I wish I knew

/management

earlier. It's genius! Nothing specific here, just wanted to give a shout-out to the prisma team for this fantastic piece of software that empowers a whole community to keep going forward with their products #graphql #prisma

Hi, I am configuring a graphcool-framework project but i would like not to use a graphcool function for the authentication but something on another node server that i manage. That's all fine except one small thing: https://github.com/prismagraphql/templates/blob/master/auth/auth0/src/auth0Authentication.js#L110 how can i build a token without generateNodeToken? because I have no

event

like the one that gc function gives.

I tried yesterday, now that I know that it seems to be a server thing, ill try again: Hello world, I have a question concerning prisma subscriptions. I have a prisma backend with subscriptions implemented and and react native frontend. When I test my subscriptions in the playground, they work just as expected. (🙌 at Prisma for getting there, prisma gets more fun every day 🙂 ). When I subscribe with my frontend using

apollo-client

, the first time I subscribe, everthing works as expected. However, when I reload my frontend and subscribe again, the subscriptions doesn't get fired any more. Now, how does prisma handle resubscriptions, and what happens to the old subscriptions when my client app is killed and relaunches, i.e. the subscription is left hanging and another subscription is called from the same client? I Glad about any input and experiences! Thanks!

How do you transform a GraphQLResolveInfo object into something that matches the db schema when your app schema is not a subset of your db schema? we have introduced boundaries for fields in the app layer (example field: (name: {canView:Boolean! message:String! value: String})) the boundary obviously doesn't exist in the db schema as that doesn't make sense, but now the info object we receive in the resolver doesn't match the db so we can't select the field, how would we strip the boundary from the info object? we also have some cases where we generate the result of a query but it contains fields that should be fetched from the db, how do we get the selection of a field in the query?

https://www.prisma.io/docs/tutorials/deploy-prisma-servers/digital-ocean-(docker-machine)-texoo9aemu

This tutorial only applies to Prisma versions lower than 1.7 and will be updated soon.

Does that mean the guide isn’t worth following with 1.9 or does it still work?

aside from this example: (https://github.com/prismagraphql/prisma/blob/master/examples/resolver-forwarding/index.js#L7), is there documentation for

prisma-binding

forwardTo

? doc search didn't find anything

Is

/graphiql

not compatible with Prisma? I can execute queries and mutations fine (locally) but when I start adding filters, it just doesn’t work. When I hit the endpoint (`http://localhost:4466/service/stage`), where service and stage are my project’s service and stage, everything works perfectly but I have no idea where the data is going.

QUESTION: I am using the super basic setup from this guide: https://www.prisma.io/docs/tutorials/setup-prisma/create-new-db/mysql-gui4peul2u/ Whenever i kill the running docker instances and restart them and then re-deploy prisma it always kills the data i have in my database. Why is it doing this and how do i prevent the loss of data when the services are killed and restarted?

I am using

docker-compose down -v && docker-compose rm -v

to kill the services

and

docker-compose up -d

and

prisma deploy

to start them back up

Anybody got issues after updating to

prisma@1.10.0

? I get this

TypeError: Invalid Version: 1.1

when I run `prisma deploy`:

Environment saving global rc +0ms
  StatusChecker setting status checker +865ms
  prisma definition making cluster here +0ms
  client Initializing cluster client +0ms
  deploy checking verions +897ms
TypeError: Invalid Version: 1.1
    at new SemVer (path/to/node_modules/semver/semver.js:305:11)
    at Range.test (path/to/node_modules/semver/semver.js:1112:15)
    at Function.satisfies (path/to/node_modules/semver/semver.js:1161:16)
    at Deploy.<anonymous> (path/to/node_modules/prisma-cli-core/src/commands/deploy/index.ts:279:38)
    at step (path/to/node_modules/prisma-cli-core/dist/commands/deploy/index.js:42:23)
    at Object.next (path/to/node_modules/prisma-cli-core/dist/commands/deploy/index.js:23:53)
    at fulfilled (path/to/node_modules/prisma-cli-core/dist/commands/deploy/index.js:14:58)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)

I created a private npm package for our graphql-binding subclass (similar to the GitHub binding) but when I pull it into my gateway API it gives the following error

Error: Cannot find module '[full path to repo root omitted]/node_modules/graphql/index.js'
  at webpackEmptyContext ([full path to repo root omitted]/packages/client-api/.webpack/service/src/webpack:[full path to repo root omitted]/node_modules/graphql-binding/dist sync:2:1)

The file it says it can’t find is definitely at that location as lots of packages in that repo depend on the graphql package

I’m thoroughly confused about this error

Has anyone else had issues with RDS instances getting overloaded with write operations from Prisma? running an r4.xlarge instance with autoscaling but still frequently hitting 87%+ CPU

Using Prisma, is there a quick and easy way to increment an Int field in a mutation (via forwardTo)?

FYI for anyone else attempting to use the recently released 1.10.0, I ran into a bug where the ’0’s get stripped off by regex and so you can’t deploy: https://github.com/prismagraphql/prisma/issues/2663

Running into an issue when I added

listing: forwardTo('db')

to my resolver. I get the following mesage:

import { GraphQLServer } from 'graphql-yoga'
import { forwardTo} from 'prisma-binding'

import { Prisma } from './generated/prisma'

Argument of type '{ typeDefs: string; resolvers: { Query: { listing: (parent: any, args: any, context: any, info: G...' is not assignable to parameter of type 'Props'.
  Types of property 'resolvers' are incompatible.
    Type '{ Query: { listing: (parent: any, args: any, context: any, info: GraphQLResolveInfo) => any; }; M...' is not assignable to type 'IResolvers'.
      Property 'Query' is incompatible with index signature.
        Type '{ listing: (parent: any, args: any, context: any, info: GraphQLResolveInfo) => any; }' is not assignable to type '(() => any) | IResolverObject | GraphQLScalarType'.
          Type '{ listing: (parent: any, args: any, context: any, info: GraphQLResolveInfo) => any; }' is not assignable to type 'GraphQLScalarType'.
            Property 'name' is missing in type '{ listing: (parent: any, args: any, context: any, info: GraphQLResolveInfo) => any; }'.

Prisma you drunk my friend http://cl.ly/2B0Y1O2D2a3M

the ol ‘10’ > ‘9’

that happened when IE10 came out

haha yep

😛

Anyone else getting this complaint after upgrading:

prisma deploy
 ▸    Invalid Version: 1.1

This is maybe a simple question... but kind of an obvious and clear one... Is there a way to get the

createdAt

and

updatedAt

fields in a Prisma schema? Like. I don't YET need it for my project, and I was thinking to myself "wow, if I do need this it's going to be a real embarrassment if I can't get information as simple as the updated and created at times for a row!" (nervous chuckling to self)

Hi, I was wondering: what if I have a field in the prisma schema that I don't want to expose. Can I white or black list those fields, like suggested here https://www.prisma.io/forum/t/create-private-field-using-directive/3669 ? I mean, I still want to store a field but I just don't want it exposed to the client. Do I then need to define that whole type but without the "private" field, like below? `database/datamodel.graphql`:

type Foo {
  foo: String
  privateBar: String
}

`src/schema.graphql`:

type Foo {
  foo: String
}

Is anyone working on graphql-request cross-fetch bundling issue with webpack https://github.com/prismagraphql/graphql-request/issues/85

Hello, fresh install for me for prisma and I have this error message

$ prisma deploy
 !    Invalid Version: 1.1

Any idea?