Anyone else having issues keeping subscriptions alive using

$subscribe

?

Is there any reference docs on the (node) prisma client? It took me about 40 mins just now to work out the difference between

await prisma.createUser(mutation)

and

prisma.createUser(mutation).id()

-- or what that was doing, and why the examples (in the codesandbox) all return plain objects

Good night people! I would like to confirm if I am right (if you can help me), so I saw the only way to do schema delegation is through the prisma-binding package, is that right? Or does the Prisma Client also provide a way to do?

Hi everyone

I have an existing mongo database And I want to connect prisma in it How can i do that ? because the prisma server always creating a new database when I deploy service in it

someone can help me?

Hi all! I am fetching this query and it is taking 5 seconds approx to return result back. I am using prisma-client. Do I need to implement dataloader with prisma or it support out of the box

As Scalar fields are returned automatically. For nested fields I am returning it like this (author & comments). Am I doing something wrong?

anyone getting a parse error when importing generated api into schema.graphql? Keep restarting with the graphql auth/shield example and getting this error:

GraphQLError: Syntax Error: Cannot parse the unexpected character ".".

It goes away when I remove this line from my schema:

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

Used this method for almost a year without issues until recently. Using prisma-client-lib v 1.25.7 Min repo: github.com/jackgray/govtrackr

Does anyone know how to get relation object in realtime (subscription) iterator? I need to get object

sender

(type User) from created message.

newMessage.sender

is

undefined

hello!

i got a trouble in prisma init

i selected existing database, mysql .. and database information

then, i got a message

Cannot read property 'startsWith' of undefined

plz, help me!

Hi. i’m having an error with my query and I’m not seeing what could be wrong

I have a schema like this

type Query {
  info: String!
  users: [User!]!
  conversations: [Conversation!]!
  conversation(id: String!): Conversation!
}

type Mutation {
  createUser(name: String!): User!
  createConversation(user1: ID!, user2: ID!): Conversation!
}

type User {
  id: ID!
  name: String!
  conversations: [Conversation!]!
}

type Conversation {
  id: ID!
  messages: [Message!]!
  users: [User!]!
}

type Message {
  id: ID!
  content: String!
  createdAt: String!
  userId: ID!
  conversation: Conversation!
}

And I have my resolvers implemented as such:

const resolvers = {
  Query: {
    info: (root, args, context) =>
      `This is the API of chatt app for Packt course`,
    users: (root, args, context) => context.prisma.users(),
    conversations: (root, args, context) => context.prisma.conversations(),
    conversation: (root, args, context) =>
      context.prisma.conversations({ id: args.id })
  },
  Mutation: {
    createUser: (root, args, context) => {
      return context.prisma.createUser({
        name: args.name
      });
    },
    createConversation: (root, args, context) => {
      return context.prisma.createConversation({
        users: {
          connect: [{ id: args.user1 }, { id: args.user2 }]
        }
      });
    }
  },
  Conversation: {
    users: (parent, args, context) => {
      console.log("calling users");
      return context.prisma.conversations({ id: parent.id }).users();
    },
    id: (parent, args, context) => parent.id
  },

  User: {
    conversations: (parent, args, context) => {
      return context.prisma.users({ id: parent.id }).conversations();
    }
  }
};

When I call the query

query {
  conversation (id: "cjta0oy64ocr60b79pevff0lw"){
    id,
    users {
      name
    }
  }
}

I get an error that says

{
  "data": null,
  "errors": [
    {
      "message": "Could not find argument id for type Conversation",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "conversation"
      ]
    }
  ]
}

I don’t know what that means

I’ve added the ID property but it seems I’m missing something

maybe I’m query prisma client wrong

I found the problem. rather than

context.prisma.conversations({ id: parent.id }).users();

I should be using

context.prisma.conversations()

Spectrum doesn't look very alive, so I'll post it here as well 🙂 Hey guys, I'm not sure if it's a bug or I'm doing something wrong, please confirm. I use postgres connector (but I've checked mysql as well and still the same issue) and prisma typescript-client generator. After I deploy my datamodel which is very simple and looks like this:

type Member {
  id: ID! @unique
  currentBalance: Float!
  transactions: [Transaction!]
  retailers: [Retailer!]
}

type Retailer {
  id: ID! @unique
  name: String!
}

type Transaction {
  id: ID! @unique
  purchaseDate: DateTime!
  rewardedDate: DateTime!
}

typescript-client generates interface without relational fields.

export interface Member {
  id: ID_Output;
  currentBalance: Float;
}

So some of my resolvers don't have necessary types 😞 Anyone already faced this? Thanks in advance!

how to send two mutations by prisma-binding ?

I have posted it in #general, but it is realted to the prisma client (maybe). Prisma is failing to export / reset / import to itself

Is it possible to use nested queries with TypeScript and prisma-client-lib? Previously with prisma-binding, it was possible to pass the info variable to the binding, but the prisma-client-lib lacks this capability.

I’ve found this blog https://medium.com/@lukehamilton/nested-relations-in-prisma-971e060a16ab

This blog helps me so far, I only have to extract the fragment from the info parameter. Are there already solutions?

Guys, what is the status of https://github.com/prisma/rfcs/blob/new-ts-client-rfc/text/0000-new-ts-client.md ?

Is any team working on implementation of prisma-client v2 ?

Can any one guide me..How i can try prisma graphQL api with rest api client like postman?