Guys, quick question to the data model: Is it possible to set a URL as default value i.e.: image: String! @default(value: "")

Right now I have defined all my DB models in separate files, and pass them all to Prisma in

prisma.yml

like this:

datamodel:
- model/user.graphql
- model/post.graphql
- model/comment.graphql
...

This becomes quite long, and also requires for the developer to remember to add the new models to this list, so I was wondering if there’s a way to create an

index.graphql

files that imports all of the models in the folder automatically?

Hi everyone - WesBos/Lydia are my reason for being here - the course from the former, the invite from the latter 🙂

Hey guys I’m Taro from Tokyo. Same as Paul, I’m here because of Wes!

Hey --- is there a way to run a prisma server via AWS Lambda/Serverless? And I’m not talking about graphql-yoga… i’m talking about the server that is the middle layer (currently a docker-compose instance) between yoga and the postgres database.

Also can someone please 🙏🙏🙏🙏🙏 explain to me how it is expected to take a prisma architecture to production? Ive been trying to get this to work for about 3 months now. I’m exceptionally familiar now with prisma server, graphql-cli, prisma-client, and now graphqlgen… but I have a client whom I’m building their app, and I can’t figure out, nor can I find docs on how to go from a local docker-compose dev instance to actual production level architecture (like on AWS). I’ve tried using the

graphql-yoga lambda-typescript

example, the

graphql create

cli flow. I’ve even tried Apex Up and Now… but why do I have to use them, and pay for their 3rd party services? I’ve been able to get Prisma-client working up on serverless… but not working, as I then have to point to a prisma server (that currently doesn’t exist, unless I use docker)…. What am I missing? Thanks!

Hello all, I'm having an issue with a graphql-yoga api server if this is the right place to ask. I am trying to turn off playground, i use the option for the server start function. It works locally and in a local run container that I am actually pushing to AWS, but in ECS when the app loads, playground is still loading up. There is no cloudfront cache in front of this endpoint. I'm stumped as to why it would work in local container and not when deployed in ECS. If anyone has run into this please let me know.

Hey guys, I'm having difficulty using a *Connection query with prisma-client (after switching from prisma-binding). When I was using prisma-binding, my query worked fine, but now i'm being told my *Connection query must have a sub-selection. I'll post details in a thread

This is pretty big news: https://www.linuxfoundation.org/press-release/2018/11/intent_to_form_graphql/

Hi everyone, I’m running same query on a same DB, any idea why they backend query returns undefined?

Has anyone integrated auth0

with prisma ?

is it possible to do an update single record mutation with a where based on multiple fields?

@Luke I have integrated auth0

with prisma

@CCBCodeMonkey do you have a code example you can share of that ?

I worked off this example

not being able to do an update on a single record with a where based on multiple things, really sucks

I want to update a post where the id = x and currentUser isOwnerOfPost

are you referring to the example above?

no

sorry, unrelated to that

okay cool

😛

@CCBCodeMonkey Thanks!

no prob

@Luke just to elaborate a bit, all of the auth0 logic is in the graphql-yoga layer

the only thing you really change with prisma is you need to update the datamodel to store the auth0 fields on your user