No that was the most helpful I found so far

I think it would be good to give tutorial that is most needed in production such as auth, fileupload, multipart upload. I am looking for these three currently.

Having issues while deploying the following:

type Mutation {
  signup(email: String!, password: String!): AuthPayload!
  login(email: String!, password: String!): AuthPayload!
}

type AuthPayload {
  token: String!
  human: Human!
}

Errors:

Errors:

  Mutation
    ✖ The relation field `signup` must specify a `@relation` directive: `@relation(name: "MyRelation")`
    ✖ The relation field `login` must specify a `@relation` directive: `@relation(name: "MyRelation")`

Don't understand what it wants ...

So does that mean that I need to copy-paste all types from data model to schema file to duplicate these?

Or is there a better way to share this? I understand that these have different purposes. One is for data modeling (i.e. database design), and the other is for defining the GraphQL types and queries. But still seems like a waste to have to duplicate.

E.g. I have an

enum

definition. It will not change from data model to schema definition.

Does anyone face this issue? https://www.prisma.io/forum/t/prisma-graphql-not-updating/2255/9

I can’t manage to update the prisma.graphql when I’ve changed datamodel.prisma and the query.

prisma.graphql

in

generated

is not updating how can I make this updated? I’ve tried

prisma deploy

.

How do I completely remove database and create again? I’ve deleted the default@default database locally and prisma deploy is failed telling me table doesn’t exists.

Hi! I want to pass another parameter along with result from graphql mutation query. However, error throws when I change my below query.

signup: async (_, args, context, info) => {
      const result = await context.prisma.mutation.createUser(
        {
          data: {
            email: args.email,
          },
        },
        info,
      );
      return result;

When I change above query to below,

Error: Cannot return null for non-nullable field User.id.

error is always throwing. No idea why this is happening.

signup: async (_, args, context, info) => {
      const token  = jwt.sign({ userId: args.id }, SECRET);
      console.log('token: ' + token);  // token always has a value!!
      const result = await context.prisma.mutation.createUser(
        {
          data: {
            email: args.email,
          },
        },
        info,
      );
      return {
        token,
        result,
      };
    }

Could anyone guide me to this problem?

How can I pass another data to result along with graphql result?

I’ve posted this in

forum

. https://www.prisma.io/forum/t/passing-another-variable-in-mutation-query/5282/2. Thank you.

Hello all how do u i know my default db where my schema update using "prisma deploy"

Hello, is @migrationValue deprecated?

Hi guys, For duration type. Do we use

DateTime

or just

Int

. I read that prisma

DateTime

uses ISO 8601 . Which support Duration https://en.wikipedia.org/wiki/ISO_8601#Durations . But when I try duration

10 minutes

PT10M

. It doesn't seems to work.

Hi all I've failed to install docker on my local. Is there any way to try prisma without docker?

Hello there. Do you guys think prisma is the right choice, if i need to make more advanced queries ( for different analytics and such .. ), with joins and aggregation methods ? Or does it actually offer the possibility of making raw sql query ?

Or is it equally effective, if i run graphql queries through prisma, and make all the grouping and calculations and anything else with nodejs ?

Hi everybody, I want to share the fastest way to have a GraphQL server connected with firebase 🔥… just need a schema and that’s it. It’s a beta release! https://twitter.com/easygraphql/status/1073012982211334144?s=20

#EFF3F5,#EFF3F5,#0C344B,#FFFFFF,#FFFFFF,#0C344B,#15bd76,#0f7ad8 Maybe someone wants a Prisma slack theme.

Hi! Is there a separate slack group to talk about the MS SQL Database Connector!

Would anyone know any progress on that connector? or somewhere I can preview it?

Why the @unique directive in datamodel doesn’t working properly ? Prisma is connected to MongoDb and everything is working good but when I add @unique directive to field and redeploy prisma, then I still can create more than one user with same email. DataModel: type User { id: ID! @id name: String! email: String @unique }😢

is there a bug or something wrong in my code ?

have you tried using

prisma reset

command first or delete your containers and then running all again?

Also if you are using the generated client you should generate it again after deploying new changes

of course I generated the client and I deleted every thing (collections in db) but the @unique directive still not work with mongodb connector 🧐

🤔

I'm loosing my mind