https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • c

    cadbot

    05/15/2017, 11:29 PM
    Also, it seems like edges are more likely to be involved with root query fields. Not sure if that is part of the equation
  • n

    nando

    05/16/2017, 3:28 AM
    👀 hello everyone
  • a

    artyom

    05/16/2017, 6:13 AM
    hi @nando 👋 also welcome @engeng and @mmoo9154 to the club! graphcool
  • a

    artyom

    05/16/2017, 6:13 AM
    check out #graphql-europe-comm if you’re here for GraphQL-Europe 🚀
  • b

    bondo

    05/16/2017, 7:15 AM
    Hi 🙂 I was just trying to create a file through the the createFile mutation and got an internal server error. My request ID is cj2r7ruyemh2p01661jptfoun
    n
    • 2
    • 4
  • n

    nish

    05/16/2017, 8:39 AM
    Hi, Can someone give his/her input on my schema design. (Still trying to think in graphs). Here is my rough application diagram with entities and users. To summarise: 1) There are 3 type of users - Application user (me), pharmacy users and client users and they have their specific roles. 2) Application can have multiple pharmacies (entity) 3) Each pharmacies can have multiple clients (entity) and vice versa 4) Each client can have multiple departments — client users can belong to either client directly or to a department 5) Pharmacy users can see all the orders made by client users 6) Only client users are allowed to make orders
  • n

    nish

    05/16/2017, 8:40 AM
    Here is my schema looks like
    Copy code
    `
    type Customer implements Node {
      createdAt: DateTime!
      departments: [Department!]! @relation(name: "DepartmentOnCustomer")
      id: ID! @isUnique
      name: String!
      orders: [Order!]! @relation(name: "OrderOnCustomer")
      pharmacies: [Pharmacy!]! @relation(name: "PharmacyOnCustomer")
      updatedAt: DateTime!
      users: [User!]! @relation(name: "UserOnCustomer")
    }
    
    type Department implements Node {
      createdAt: DateTime!
      customer: Customer @relation(name: "DepartmentOnCustomer")
      id: ID! @isUnique
      name: String! @isUnique
      updatedAt: DateTime!
      users: [User!]! @relation(name: "UserOnDepartment")
    }
    
    type File implements Node {
      contentType: String!
      createdAt: DateTime!
      id: ID! @isUnique
      name: String!
      secret: String! @isUnique
      size: Int!
      updatedAt: DateTime!
      url: String! @isUnique
    }
    
    type Order implements Node {
      createdAt: DateTime!
      customer: Customer @relation(name: "OrderOnCustomer")
      id: ID! @isUnique
      info: String
      pharmacy: Pharmacy @relation(name: "OrderOnPharmacy")
      status: Int!
      updatedAt: DateTime!
      user: User @relation(name: "OrderOnUser")
    }
    
    type Pharmacy implements Node {
      createdAt: DateTime!
      customers: [Customer!]! @relation(name: "PharmacyOnCustomer")
      id: ID! @isUnique
      name: String! @isUnique @defaultValue(value: "")
      orders: [Order!]! @relation(name: "OrderOnPharmacy")
      products: [Product!]! @relation(name: "ProductOnPharmacy")
      updatedAt: DateTime!
      users: [User!]! @relation(name: "UserOnPharmacy")
    }
    
    type Product implements Node {
      code: String @isUnique
      codeVnr: Int!
      createdAt: DateTime!
      form: String
      id: ID! @isUnique
      manufacturer: String
      name: String!
      nameFull: String!
      package: String
      pharmacy: Pharmacy @relation(name: "ProductOnPharmacy")
      strength: String
      type: Int!
      updatedAt: DateTime!
    }
    
    enum ROLE {
      EM_SUPERADMIN
      EM_ADMIN
      P_ADMIN
      P_MODERATOR
      P_MEMBER
      C_ADMIN
      C_MODERATOR
      C_MEMBER
    }
    
    type User implements Node {
      createdAt: DateTime!
      customer: Customer @relation(name: "UserOnCustomer")
      departments: [Department!]! @relation(name: "UserOnDepartment")
      email: String @isUnique
      firstName: String!
      id: ID! @isUnique
      info: String
      isActive: Boolean! @defaultValue(value: true)
      lastName: String!
      orders: [Order!]! @relation(name: "OrderOnUser")
      passwordChanged: Boolean! @defaultValue(value: false)
      pharmacy: Pharmacy @relation(name: "UserOnPharmacy")
      phone: String @isUnique
      role: ROLE!
      updatedAt: DateTime!
      url: String @isUnique
    }
  • n

    nish

    05/16/2017, 8:42 AM
    I am wondering if I am cluttering
    User
    node too much. Should I go with the aforementioned schema design or create new
    Types
    , which maps the relation between
    pharmacy - client
    ,
    pharmacy user - pharmacy
    ,
    client user - client
  • s

    sdubois

    05/16/2017, 9:28 AM
    Hi and thanks for the new graphcool CLI! I'm not quite sure how I should pull the config file for an existing endpoint? Doing
    graphcool pull <project_name>
    I got
    Error: <project_name> is not a valid project file (must end with .graphcool).
  • n

    nilan

    05/16/2017, 9:29 AM
    have a look at
    graphcool pull -h
    🙂
    s
    • 2
    • 2
  • n

    notrab

    05/16/2017, 9:30 AM
    I hope you guys don’t mind but I hunted you on ProductHunt https://www.producthunt.com/posts/graphcool-2 😄 🔥
    🙏 3
    😎 3
    🏹 1
    🚀 4
    🤘 1
    graphcool 7
    ❤️ 2
    🦜 4
  • s

    sorenbs

    05/16/2017, 9:31 AM
    Thanks a lot Jamie!
  • j

    jensneuse

    05/16/2017, 9:41 AM
    @notrab Sounds like you are not using a popkiller?
    n
    • 2
    • 2
  • n

    notrab

    05/16/2017, 9:41 AM
    Popkiller?
  • j

    joar

    05/16/2017, 9:41 AM
    @jensneuse whats a popkiller? never heard that term before
  • j

    jensneuse

    05/16/2017, 9:42 AM
    it prevents “popping” sounds when air hits the microphone during speaking/breathing
  • n

    notrab

    05/16/2017, 9:43 AM
    Oh, are you on about the YouTube video? That isn’t me. I got the video from Graphcool youtube 😄
  • j

    jensneuse

    05/16/2017, 9:43 AM
    yes, okay
  • j

    jensneuse

    05/16/2017, 9:44 AM
    Sorry, then it’s dedicated to the video author. 😃
    🙂 1
  • j

    jensneuse

    05/16/2017, 9:45 AM
    it’s 20 bucks well invested when making videos/webinars etc.
  • a

    artyom

    05/16/2017, 9:53 AM
    this would be for @nikolasburk ☝️
  • n

    nikolasburk

    05/16/2017, 10:00 AM
    ⚠️ Hi everyone! ⚠️ We would definitely appreciate your support on Product Hunt! 🚀 To make sure you’re actually supporting us with an upvote, please do not use the direct product hunt link that’s posted above - otherwise the votes might be considered part of a “voting ring”. So please go to Product Hunt and find Graphcool in the Today section. Thanks!! 🙏 graphcool
    🙇 2
    🙌 1
    ☝️ 2
    🙏 3
  • a

    artyom

    05/16/2017, 11:12 AM
    @eddymens @aldrian @j0k @idkjsx @sunilshenoy @gokatz @webtaculars hello there and welcome all to graphcool , nice to have you here!
    ❤️ 1
  • a

    artyom

    05/16/2017, 11:13 AM
    if you’re here for GraphQL-Europe, head over to #graphql-europe-comm for the latest and greatest! graphql europe
  • g

    gokatz

    05/16/2017, 11:15 AM
    Hi @artyom
    👋 1
  • g

    gokatz

    05/16/2017, 11:16 AM
    I'm a pure front-end guy.. Where can I find some docs ?
    a
    k
    • 3
    • 5
  • j

    joar

    05/16/2017, 11:30 AM
    👆 spam?
  • a

    aldrian

    05/16/2017, 12:26 PM
    Hi! Is there any admin interface recommended for graph.cool?
    h
    v
    s
    • 4
    • 6
  • j

    jdspugh

    05/16/2017, 1:39 PM
    Great job, Graph.Cool team. You have created a database the way it was always meant to be. A joy to work with.
    ❤️ 3
    a
    m
    • 3
    • 4
  • n

    notrab

    05/16/2017, 1:41 PM
    Functions aren't showing in the Console for me yet. Cache issue or is there a problem?
    n
    • 2
    • 2
1...187188189...637Latest