https://www.prisma.io/ logo
Join Slack
Powered by
# orm-help
  • l
    becauser 
    User
    isn’t an embedded type, you need to specify the relationship between 
    User
    and 
    Company
  • n
    So how do I specify it to the 
    id
    of the user?
  • l
    Copy code
    type User {
    id: ID! @id
}

type Company {
    id: ID! @id
    createdBy: User
    members: [User!]! @relation(link: INLINE)
}
  • l
    now you should be able to add 
    Users
    to your 
    Company
  • n
    Thanks already for the help 👍 . Can you explain what an "embedded" type is?
  • n
    Because don't see a difference between the relation of createdBy or members in the example
  • l
    basically an 
    @embedded
    type is something that exists only inside a certain collection/table
  • l
    here’s an example:
    Copy code
    type User {
    id: ID! @id
    profile: UserProfile
}

type UserProfile @embedded {
   name: String
}

type Company {
    id: ID! @id
    createdBy: User
    members: [User!]! @relation(link: INLINE)
}
  • l
    in this example, 
    UserProfile
    doesn’t have its own collection/table like 
    User
    and 
    Company
    does
  • l
    it only exists as the definition of the profile object for a 
    User
  • l
    therefore, it’s an embedded type
  • n
    Didn't know that was possible 🙂
  • n
    But in the example I have we don't specify 
    @relation
    for 
    createdBy
    but we need to for 
    members
    , what is the difference then? Because the 
    User
    type is not an embedded type
  • l
    good point
  • l
    i have a hard time understanding why it wouldn’t show you an error since you would technically need the 
    @relation
    as well
  • l
    but maybe it’s not showing you an error because it’s not specified as required
  • l
    unlike 
    members
  • l
    that’s my guess
  • n
    Doesn't 
    [User!]!
    mean that it can be empty as well?
  • l
    yes
  • n
    So members is not required then right?
  • l
    an array is required, but the array can be empty
  • n
    So how do I specify the 
    @relation
    to the 
    id
    of the 
    User
    type?
  • n
    This is btw the exact error I receive, it basically says I can only use a relation with a name, so no 
    INLINE
    Copy code
    × The relation field `createdBy` must specify a `@relation` directive: `@relation(name: "MyRelation")`
× The relation field `members` must specify a `@relation` directive: `@relation(name: "MyRelation")`
    l
    j
    • 3
    • 64
  • s
    Getting this error when I try to run npm run get-schema 
    Your token is invalid.
    Here is my package.json scripts:
    Copy code
    "scripts": {
    "start": "nodemon src/index.js --ext js,graphql --exec babel-node",
    "get-schema": "graphql get-schema -p prisma"
  },
    Here is my .graphqlconfig
    Copy code
    {
  "projects": {
    "prisma": {
      "schemaPath": "src/generated/prisma.graphql",
      "extensions": {
        "prisma": "prisma/prisma.yml",
        "endpoints": {
          "default": {
            "url": "<http://192.168.99.100:4466>",
            "headers": {
              "Authorization": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkYXRhIjp7InNlcnZpY2UiOiJkZWZhdWx0QGRlZmF1bHQiLCJyb2xlcyI6WyJhZG1pbiJdfSwiaWF0IjoxNTY1OTA4MTQ1LCJleHAiOjE1NjY1MTI5NDV9.UWO9S9avS-VzY_g9X3Uqo66qVvQtQsVUZkeT5dngaoA"
            }
          }
        }
      }
    }
  }
}
    And here is my project architecture:

    https://i.gyazo.com/75f023922fef9a91d8e8f368c69c441f.png▾

  • a
    What would be the best way to do this query on Prisma 1: Delete all users with less than 3 written posts? type User { id: ID! writtenPosts: [Post!]! @relation(name: "WrittenPosts") } type Post { id: ID! author: User @relation(name: "WrittenPosts") content: String! }
    ❓ 1
  • r
    is there a way in Nexus to use context to resolve an interface type?
  • a
    aws fargate prisma Hello everybody. In AWS Fargate I run two services, a prisma server and a graphql server (using apollo-server-express, graphql-middleware and cors). I don't understand why I got this error in chrome (v76) everytime I made a request from client side (first image). This is my configuration from server (second image). Thanks in advance for any hint.
    a
    j
    • 3
    • 4
  • a
    Hello. Unfortunately I am struggling a bit to get calculated fields resolved when using prisma bindings or prisma clients and fragments (works with info object). Imagine I want to calculate a hmac from the email of a User type. I add a custom resolver called hmac in the User resolver and add hmac to the User type in the schema.graphql. Now I can query the hmac from the frontend using the info object and it will be returned without a problem. If however I am trying to resolve / receive this calculated value from a fragment I will receive an error like "Cannot query field 'hmac' on type 'User'." Code: const user: any = await prisma .user({ id: ctx.req.userId, }) .$fragment(
    Copy code
    fragment UserWithPosts on User {
          id
          email
          hmac
        }
    ); What am I doing wrong? How to receive custom resolver values using fragments / the prisma client or binding?
  • c
    Anyone have any experience trying to export the data from the prisma.io DBs? HOw would one go about doing this if they wanted to migrate from one infrastructure to another?
    a
    • 2
    • 1
1...301302303...637Latest