hello guys!!

I am workin with Prisma

How can I add authorizations to some resolvers?

Anyone know how to disable Prisma caching of requests?

I have that same question

Are there multiple cache layers? Like one on the server and one on the cluster or something?

Will be there recordings from conference?

see #graphql-europe

Hey guys, just wondering if prisma has (or plans to have) hooks? i.e. your typical beforeCRUD/afterCRUD filters that would allow to alter behaviour based on business logic requirements

One of our graphql projects uses sequelize and, for example, we have hooks to make sure update requests don't actually update records but create revisions - this is all invisible to the api client and it's done through sequelize hooks

other things I could think about are more complex scenarios that would require single table inheritance etc.

you're gonna have to implement that yourself

prisma is just the database, nothing else

I've created a simple prisma service by using

prisma init

but when I do

prisma deploy

it doesn't show up in the prisma console. What am I missing?

Hey guys, I read at multiple occasions, that the .env file in a prisma project should be edited? I don't have one. Is it necessary to eject the project first?

hey guys, I’m using graphql-yoga and prisma that is deployed to my own cluster and I’m running into some really bad latency issues. Each request is 5s+ on my frontend, but the curious thing is prisma itself is pretty fast when queried from the playground. Any ideas what could be wrong? I’m using prisma bindings in my resolvers

Hello everybody, I might need some advice. I followed @max's tutorial here: https://github.com/maxdarque/prisma-docker to set up a root server, which runs the mysql instance natively without docker. Besides that, the root server shall host my frontend, the prisma server and the graphql-yoga server. I know of the performance issues, this will probably create, but it's only for the beginning. Later on, I will probably hop on a dedicated AWS service for every server and the db. Now my issue: I created the docker container with docker-compose and connected to my db via the necessary credentials. Afterwards I created a subfolder within the directory with the docker-compose.yml by initializing the prisma project with prisma init. I deployed the prisma project to my created cluster, but even though I set up an external db for this, it still uses the (on deploy) freshly created default db, when I start the graphql server with yarn start. Any ideas, what could cause this? Thanks to everyone in advance!

Hello. I've setup the advanced boilerplate from https://github.com/graphql-boilerplates/typescript-graphql-server which uses graphql-yoga. I'm attempting to use the playground to register a user and then query for

me

. However, I have no idea at all how to utilize the token that is provided from the login mutation when running any of the authentication requiring queries.

Anyone have experience with aws lambda with prisma?

@ldlework In the playground you can add the token to the 'Authorization' HTTP header for your query requests. Take a look at this screen shot.

@Mike Clymer commented on @Mike Clymer’s file : @Idlework I am also making the assumption that you are using the getUserId(...) function provided in https://github.com/graphql-boilerplates/typescript-graphql-server/blob/master/advanced/src/utils.ts

@Mike Clymer oh wow I did not even notice this pane at the bottom!

I am wanting to use aws lambda to run every 2 hours to fetch data and save it to database, any suggestion on this? I could have 1000 records to upsert at a time.

Any resources I could use for serverless with prisma?

@glen Yeah i know about this but I am trying to figure out the best way to fetch my data and insert the data. I am doing a real estate site, so I am not sure if the lambda function will handle all that data.

I can only fetch for 1500 records. I have to loop through several times to get the data, then I have to map the data to it's keys. But I don't think prisma does a batch write so I guess I have to run a loop to write each of the data.

Hello, we had a strange function invocation that occurred around midnight UTC, but cannot find the logs for that function invocation anywhere

Is this a known issue?

Any idea why context.headers would be undefined in a custom directive? I’m using https://www.apollographql.com/docs/graphql-tools/schema-directives.html#Enforcing-access-permissions as an example