I don't get the invalidArgs

so I can match it up on the UI

I'm getting some weird issue that I haven't had before so I'm using the graphql boilerplate that and the genrated file prisma.graphql Does not update

Hi here. I want to implement voting functionality in my app. A video can only have one vote per user. Is there a way to set this limitation in prisma datamodel? I mean so that a user can not vote a video multiple times. Or the only way to do this is to check if a video already has a vote by this user in

votePost

resolver? My current datamodel is the following:

type Video {
  ...
  votes: [Vote!]! @relation(name: "VideoVotes")
  voteScore: Int! @default(value: 0)
}

type Vote {
  id: ID! @unique
  parent: Video! @relation(name: "VideoVotes")
  user: User! @relation(name: "UserVotes")
  type: VoteType!
}

type User {
  ...
  votes: [Vote!]! @relation(name: "UserVotes")
}

enum VoteType {
  UP
  DOWN
}

you could put a combined unique key on parent and user in the vote type (dont know if prisma supports this) - that would be the way i implement this in my database manually

but you would still have to check if it exists i guess.. it would just deny you from writing a second entry

I’m having some issues when running

prisma generate

and it not doing _anything_… no generated files, no errors, nothing.

I need to configure readiness and liveness probes for my kubernetes cluster. Mainly because the yoga server only handles post request and hence the std way using get requests is not working, Therefore i was wondering if any of you have tried to use lightship (https://github.com/gajus/lightship#using-with-expressjs) with graphql-yoga? Looks very simple with express server but I do not know how to do it with yoga? I see that I can "eject" (https://github.com/prisma/graphql-yoga#how-to-eject-from-the-standard-express-setup) the express setup but I do not understand what that means to be honest 🙂

updatedAt

field is not working. I am seeing the same issue as reported in this bug in a later version. Is this bug still an issue? https://github.com/prisma/prisma/issues/2539

is it possible to generate multiple schemas with prisma? We have several internal departments and I’d like to be able to manage all the schemas in one place but separated for each department

does anyone use apollo errors with prisma/graphql yoga

Does anyone tried to migrate data from graphcool to prisma? I am having some trouble to export graphcool data.

Prisma auto generates types for queries and mutations. Are we able to import those mutations into yoga?

anyone else see this typescript error?:

[at-loader] ./src/utils.ts:81:19
    TS2345: Argument of type '"{ role }"' is not assignable to parameter of type '{ [key: string]: any; } | undefined'.

It seems the typescript doesn't like when I pass a string into a query/mutation instead of the

info

object.

Just noticed that Prisma claims to support Mongodb but the cli tools doesn’t allows me to setup a new project with Mongo. Any recommended guide?

Anyone using prisma server on heroku? I just deployed prisma-server and I am receiving the following error:

Error R14 (Memory quota exceeded) 
Process running mem=568M(111.1%)

@Naka Upgrade your dyno, it just ran out of memory.

I think it should not be necessary, I mean... I just deployed the prisma server and tried to access from console. Upgrading to Hobby does not increase memory, it should be necessary to update to the next plan... standard that costs 25$+

Digital Ocean is cheaper

I know that upgrading should probably solve the issue... but the prisma server really consumes that much of memory just on deploy and console access?

does anyone know how to send validation errors back with throw? so the client can parse them?

like

too many characters in field x

field: x

Is there a tool like this https://github.com/EasyGraphQL/easygraphql-tester but for Prisma?

This has an issue where it can’t read the generated schema file because it is too big. And it doesn’t support

IDL style imports

. But the concept/idea is sane…. so was wondering if anyone used something like this for Prisma.

Hi does anyone know if it’s possible to have a relationship where there isn’t a “backrelation”

In other words, if I have user and post types and want a relation field, can I have an “author” field on the post type without having the corresponding “posts” in the user type?

One more question... Anyone having problems with queries on prisma console? It seems that the console search add the

id_contains

in your where variables and it is breaking the query.

Hi I am using Prisma server and want to create custom subscriptions. My data model is defined in

schema.graphql

and it has all Types in there, and I know that Prisma automatically creates queries, mutations and subscriptions for me, but I want to define my own subscription. Tried doing is inside of

schema.graphql

like

type Subscription...

but when I run it in here https://us1.prisma.sh/nevena-djaja/explorer-graphql/dev I get

"The provided query doesn't include any known model name. Please check for the latest subscriptions API."

Any ideas how to solve this?

Hey guys my makePrismaClientClass in the auto generated code from Prisma expects a models argument: Property 'models' is missing in type '{ typeDefs: string; endpoint: string; }'. Following the guide to the letter

hello, I am trying to figure out the right way to express some relationships in my schema as well as the resolvers that map to it. Could use some help and guidance! Relevant schema:

type MemberForm {
  id: ID! @unique
  name: String! @unique
  description: String
  formEntries: [MemberFormEntry!]!
}

type MemberFormEntry {
  id: ID! @unique
  form: [MemberForm!]!
  formItem: MemberFormItem!
  required: Boolean @default(value: "false")
  weight: Int
  label: String
  placeholder: String
  hint: String
}

type MemberFormItem {
  id: ID! @unique
  name: String! @unique
  kind: FormItemKind @default(value: "TEXT")
  formEntry: MemberFormEntry
}

relevant api schema:

# import {} from './generated/prisma.graphql'
type Query {
  memberForms: [MemberForm!]!
}

relevant resolver:

memberForms: (parent, args, ctx, info) => ctx.db.query.memberForms(info)

However, when I run the following query, I don’t get any

formEntries

back:

memberForms {
  id
  formEntries {
    id
  }
}