https://www.prisma.io/ logo
Join SlackCommunities
Powered by
# orm-help
  • w
    hi im trying to figure out how to update many to many relations. this is my schema
    Copy code
    type Product @model {
  id: ID! @unique
  objectID: String! @unique
  title: String!
  vendor: String
  productType: String
  categories: [String!]!
  hierarchicalCategories: Json
  createdAt: DateTime!
  updatedAt: DateTime!
  productTags: [String!]!
  price: Float
  priceRange: String
  productImage: String
  handle: String
  sites: [Site!]! @relation(name: "SitesProducts")
}

type Site @model {
  id: ID! @unique
  createdAt: DateTime!
  name: String!
  posts: [Post!]! @relation(name: "SiteOnPost")
  products: [Product!]! @relation(name: "SitesProducts")
  template: String
  user: User! @relation(name: "UserOnSite")
}
  • w
    and this is my nodejs code
    Copy code
    async addProduct(parent, args, context) {
    const productExists = await context.prisma.$exists.product({
      id: args.productId
    });
    const siteExists = await context.prisma.$<http://exists.site|exists.site>({
      id: args.siteId
    });
    console.log(productExists, siteExists);
    return context.prisma.updateProduct({
      data: {
        sites: {
          connect: {
            id: args.siteId
          }
        }
      },
      where: {
        id: args.productId
      }
    });
  },
    j
    h
    • 3
    • 9
  • w
    i dont get why its not working
  • w
    this is the result from the query
  • w
    Copy code
    {
  "data": {
    "addProduct": {
      "id": "cjscyznfh00m00855o231856w",
      "sites": null
    }
  }
}
  • b
    I would like to check for correct auth/permissions before a user can access my Prisma forwardTo(‘db’) API
    Copy code
    posts: forwardTo('db')
    What’s the best approach to handle this?
    j
    h
    • 3
    • 3
  • a
    Hi guys
  • a
    How do you auto-generate the Resolver types in typescript after adding a mutation or query root field in the schema?
    h
    • 2
    • 2
  • l
    I have a products type which has a relationship to a designers type and a relationship to a colors type, is it possible make a query to products to get a list/array of all designers on products that are blue?
    h
    • 2
    • 22
  • d
    Is anyone using Prisma in Production and dealing with the HUGE required field migrations flaw?
    h
    • 2
    • 1
  • d
    Looking for a deployment flow when adding new fields that are required in the datamodel, so far its a 3 step process that would be hard to automate with CircleCI
  • l
    How is the n+1 problem solved with prisma? I tried running a query:
    Copy code
    query {
  workspaces {
    id
    title
    workers {
      id
      name
    }
  }
}
    Resolvers:
    Copy code
    {
  Query: {
    workspaces: (parent, args, ctx) => {
      return ctx.prisma.workspaces();
    }
  },
  Workspace: {
    workers: (parent, args, ctx) => {
      return ctx.prisma
        .workspace({
          id: parent.id
        })
        .workers();
    }
  }
}
    But looking at the debug output it does'nt seem to solve the problem at all:
    Copy code
    Query:
{
  workspaces {
    id
    title
  }
}


Query:
query ($where: WorkspaceWhereUniqueInput!) {
  workspace(where: $where) {
    workers {
      id
      name
    }
  }
}

Variables:
{"where":{"id":"cjsd9u584000b07629ei22dpc"}}

Query:
query ($where: WorkspaceWhereUniqueInput!) {
  workspace(where: $where) {
    workers {
      id
      name
    }
  }
}

Variables:
{"where":{"id":"cjsdab6s8000p0762vxhtca4d"}}
    Am i doing something wrong?
    👍 1
  • l
    Nope, Prisma sadly doesn't optimize this yet (but plans to do so in the future), also see https://github.com/prisma/prisma/issues/4029
  • l
    Really?! What do the mean when they say:
    Prisma client has a built-in dataloader, solving the N+1 problem and ensuring the Prisma API is queried efficiently.
    🤔 1
    d
    t
    • 3
    • 8
  • u
    can you use more than one prisma endpoint with prisma-nexus?
    w
    • 2
    • 4
  • r
    Has anyone had issues with subscriptions not firing? I'm using them to trigger welcome emails for users, but inconsistently don't always fire.
    h
    • 2
    • 27
  • d
    Hi Prisma team, Is the following repo mantained https://github.com/prisma/serverless-plugin-typescript. I have a pull request sitting there for a while. If you guys dont have time to mantain it I could do it as it needs some fixes 🙂 Thanks -David
    t
    • 2
    • 1
  • a
    Hi guys, i don't know if anyone can help me trace this bug or solve this error I'm getting in the palyground
    h
    • 2
    • 1
  • a
    Copy code
    {
  "data": null,
  "errors": [
    {
      "message": "context.request.get is not a function",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "profile"
      ]
    }
  ]
}
  • a
    here is my helper function
  • a
    Copy code
    import jwt from "jsonwebtoken";

import { Context } from ".";

export const APP_SECRET = "GraphQL-is-awesome";

export function getUserId(context: Context): string {
  const bearerToken = context.request.get("Authorization");

  if (!bearerToken) {
    throw new Error("Not Authenticated");
  }

  const token: string = bearerToken.replace("Bearer", "");

  const userId: string = jwt.verify(token, APP_SECRET) as string;

  return userId;
}
    i
    • 2
    • 1
  • a
    @Harshit
  • j
    Hey everyone, I have a bit of an elementary question here. I have an app where you can signup, and then create a property. the /properties page is a list of all the properties you have created. My issue is now is all of these properties are visible to every user (whether or not they created the property or not). How do I only display properties that were created by that user? Is there a common pattern for this anywhere? I created the connection in my resolver, so the database is aware of which properties belong to who. Any tips would be great 🙂
    h
    d
    • 3
    • 12
  • t
    Hello there, So I finished my course of GraphQL + Prisma + Postgres, and I don’t know if I am ready to change NodeJS + Mongoose + MongoDB… to GraphQL + Prisma. Because my job is related to Web API and offline API, and when I use GraphQL I have to write the NodeJS layer yet, so why should I use ? I think the only positive point, it is because I can fetch all data that I need in just one request, is it really an advantage that makes me change how I work ? I am confused ? What do you think about it ?
    h
    • 2
    • 3
  • t
    * So, when I write an API using GraphQL + Prisma, I have to use Apollo client, and a converter of graphql query to a .get or .post request, this is more code in my app.
  • l
    Any one using prisma in a multi-tenant setup?
    l
    j
    +3
    • 6
    • 44
  • m
    Ding dong can someone please look at this PR? It's probably breaking a lot of packages for a lot of people... https://github.com/prisma/graphql-playground/pull/960
    h
    h
    • 3
    • 3
  • m
    Zero comments for 12 days now both on the issue and the PR
  • t
    qq on subscriptions that I didn’t find in the documentation. Are the subscriptions supposed to trigger If I the database is updated outside of prisma? I have 2 servers that are connected to the same DB. I want my prisma client to receive the sub events when anything is updated on the DB. Is this possible to do?
  • m
    Hi to all! Is possible to overwrite a string property from SDL and expose it as enum with nexus? I have tried this code, hiding the main 
    type
    string property, and creating a new one based on an enum. But when I try a query, when it's parsing the response, it throws an error. 
    "Expected a value of type \"CostType\" but received: \"MAINTENANCE\"",
    because it's not converting the string to the enum. How can I do it in its resolve function to convert this string to its enum?
    -.cpp
1...214215216...637Latest