I need to use another ORM on the data, the tables that Prisma create, makes it difficult to be accessed using the ORM

Hi guys, how do we share code here? I'm new here so a way on where to read about it or go about it would do just fine

Is there a way to get full stacktraces included in graphql errors when there's an exception (for development)? Currently only shows the error

hello everyone, am puzzled on how prisma generated random string for ID, i want to generate something like that can any one point me to the right direction

Thanks

Has anyone had problems calling mutations in graphql playground? I keep getting data type is not defined and it seems like grapqhly playground won't let me pass a data field

hey guys .. any idea if aws aurora is supported implicitly be supporting mysql and postgs?

any updates on using geoqueries on prisma? or a alternative way? im using algolia but have over 100k records 😕

Hello everyone

I’m not sure why I am receiving the following error:

Error: The type of Mutation.signup(data:) must be Input Type but got: SignupInput!.

I’ve defined the type in my schema.graphql:

# import * from './generated/prisma-client/prisma.graphql'

type SuccessMessage {
  message: String
}

type Mutation {
  createProperty(title: String, url: String): Property!
  signup(data: SignupInput!): AuthPayload!
  signin(email: String!, password: String!): AuthPayload!
  signout: SuccessMessage
  requestPasswordReset(email: String!): SuccessMessage
  resetPassword(resetToken: String!, password: String!, passwordConfirmation: String!): User!
  confirmEmail(email: String!, emailConfirmToken: String!): AuthPayload!
}

type AuthPayload {
  token: String!
  user: User!
}

type Query {
  properties: [Property]!
  currentUser: User
}

type SignupInput {
  name: String
  email: String!
  password: String!
}

type User {
  id: ID!
  name: String!
  email: String!
  emailConfirmed: Boolean!
  permissions: [Permission!]!
}

What am I missing here?

This message was deleted.

Hi guys

I guess i got a bug in my helper function, getUserId. As I've been following the beginner guide on node.js and GraphQL on the howtographql.com website.

I believe the issue is about the token verification in this helper function.

that's the error that returns in the graphql playground

the post mutation that makes use of the getUserId helper function in the util.js file

I really need someone to assist me troubleshoot the logic. I'm failing to trace the bug

hi I need help? how setup prisma wish my app inside one docker-compose file??like app its a service what dependet on prisma

"Note that Prisma creates a new MongoDB database for each combination of service name and stage. " => https://www.prisma.io/docs/releases-and-maintenance/features-in-preview/mongodb-b6o5/#1.-setup should this still work? Tried to deploy http://localhost:4466/api/dev and http://localhost:4466/api/test and both read from same database (stage is not even in the name)

Any clue as to why I’m getting this error?

"message": "Variable \"$_v0_data\" got invalid value { activationToken: \"b6f9bbcf6e798a87fc65c50b6d8519f3514161b6\", activationTokenExpiry: 1548952935887 }; Field value.email of required type String! was not provided.\nVariable \"$_v0_data\" got invalid value { activationToken: \"b6f9bbcf6e798a87fc65c50b6d8519f3514161b6\", activationTokenExpiry: 1548952935887 }; Field value.password of required type String! was not provided."

Here’s my schema.graphql:

# import * from './generated/prisma-client/prisma.graphql'

type SuccessMessage {
  message: String
}

type Mutation {
  createProperty(title: String, url: String): Property!
 
  signup(email: String!): SuccessMessage
 
  accountActivation(activationToken: String!, url: String, name: String, password: String!, passwordConfirmation: String! ): User!
 
  signin(email: String!, password: String!): User!
  signout: SuccessMessage
  
  requestPasswordReset(email: String!): SuccessMessage
  resetPassword(resetToken: String!, password: String!, passwordConfirmation: String!): User!
}

type Query {
  properties: [Property]!
  currentUser: User
}


type User {
  id: ID!
  name: String!
  email: String!
  permissions: [Permission!]!
}

And here’s my query on the client side:

const SIGNUP_MUTATION = gql`
  mutation SIGNUP_MUTATION($email: String!) {
    signup(email: $email) {
      message
    }
  }
`;

In the backend, i’m trying to get an email to send when a user signs up. I don’t want to store any data until the user validates their email.

Hi all, I could not find any information regarding how is the recommended way to deploy RabbitMQ for Prisma: should I use a dedicated RabbitMQ cluster just for Prisma, or can I use an existing RabbitMQ cluster? Is there a way to customize the queue names (and things like that) so that I can point more than one Prisma deployment to the same RabbitMQ cluster (and not having messages for each Prisma deployment conflicting with each other)?

i'm considering using Prisma as the DAL atop MongoDB for a new company i've founded, and it generally looks extremely well done, but i'm having trouble figuring out how & where i'd handle authentication + authorization with the stack. Prisma pretty much autogenerates all of your resolvers and server logic for you. from my understanding, you can either then wrap the Prisma server / DAL with your own server that handles auth and is a go-between, but this seems excessive since most of what you're doing in that go-between server would just be acting as a direct proxy... is it possible / advisable to expose the prisma server directly to my web + mobile clients?

does anyone know this error ?

hey guys, trying to query my app for

events

where the

startTime

field is a certain day, passed to the resolver as

date = '2019-01-31'

. simply doing

prisma.events({ where: { startTime: date } })

returns no results even though I only have events from this date.

hey everyone ... we are setting up prisma using the docker image on docker hub ... and a mysql image ... what i see is that prisma creates 2 databases (prisma & default@default) ... my fear at the moment is that in production we will need to setup one db only (an aws rds endpoint) ... how will this work?

I updated prisma to 1.25.4 and I don’t see the “set” nested mutation, is this normal ?

beta too