https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • m
    😞
    Copy code
    $ graphcool deploy
ERROR: GraphQL Error (Code: 504)
    m
    • 2
    • 1
  • m
    I am getting the same error sadparrot.
  • g
    It’s acting very buggy.
  • h
    Hey Guys!
  • j
    HeyGuys
  • j
    Anyone have a resource on schema design?
  • h
    I am new to graphql. Could you provide me some getting started resource on graphcool?
    r
    • 2
    • 2
  • j
    I have a super nested structure that I'm wondering if or how I should flatten. A -> (few) B, B -> (few) C, C -> (few) D, D -> (many) E, E -> (many) F. If I have an F and want to find it's A, I have to go through the whole stack.
  • n
    Docs are down
  • r
    @Josh Willis Nested as Subdocs such as something in a Mongo Collection?
  • j
    Is that possible in the graphcool interface?
  • j
    I could have an array of JSON objects, but that says nothing about their structure
  • r
    Yeah, the best way is to create a Type for each tier / item class then do Relationships
  • r
    the nesting can occur when you resolve those items, but want to think about things in terms of their base type
  • n
    I'm getting main.977cd8ff.js:1 TypeError: Cannot read property 'paragraphs' of null at t.render (main.977cd8ff.js:1) at r (main.977cd8ff.js:1) at r (main.977cd8ff.js:1) at i (main.977cd8ff.js:1) at o (main.977cd8ff.js:1) at main.977cd8ff.js:1 at <anonymous>
  • j
    Right, which is what I've done so far. But then if I'm at the bottom and need my great-grandparents doc fields, I have to go through all of the other parents
  • r
    can you provide an example? (if need to upload code, maybe open up topic on forum and we can help in comments)
  • j
    If you look at the answer here, you'll see a list of patterns for tree structures in a NoSQL DB. https://softwareengineering.stackexchange.com/questions/241012/how-to-represent-a-tree-structure-in-nosql
  • j
    I currently have the parent reference pattern, which is what you suggested
  • n
    OK, docs do not work on Chrome. They do work on Safari.
  • r
    Often, a custom resolver could leverage a cache (KVS, Graph DB etc.) to do fast lookups up/down a tree
  • j
    I'm wondering if it's possible to get the array of ancestors or another pattern
  • n
    Anyone seeing that docs are down on Chrome?
  • n
  • r
    you can do queries with as much nested items as are realted
  • j
    But is that the "correct" or "best" way to do it?
  • r
    it’s simply how it will work.
  • r
    Best or Correct is more based on use-case.
  • n
    I will open an issue if the docs are on github?
  • r
    Nick, I usually find they come back up eventually
1...462463464...637Latest