hey guys, I have what is basically a nested data s...
# prisma-whats-newh
horia.ancas
02/21/2018, 7:31 PMhey guys, I have what is basically a nested data structure that I would like to represent normalised. This is why I’d like to create a relationship between two fields in the same type. Let me know if this is doable or if there’s any alternative approach
Copy code
type Sample {
id: ID! @unique
graph: Graph!
content: String!
parent: Sample! @relation(name: "IsThisCrazy")
children: [Sample!]! @relation(name: "IsThisCrazy")
}r
rcy
02/21/2018, 7:36 PMHi... I have a project that makes heavy use of graph data like this
rcy
02/21/2018, 7:36 PMwe created a Relation model that connects 2 Nodes
rcy
02/21/2018, 7:38 PM Copy code
type AssetNode @model {
id: ID! @isUnique
dependencies: [AssetRelation!]! @relation(name: "NodeAOnAssetRelation")
dependents: [AssetRelation!]! @relation(name: "NodeBOnAssetRelation")
}
type AssetRelation @model {
id: ID! @isUnique
nodeA: AssetNode @relation(name: "NodeAOnAssetRelation")
nodeB: AssetNode @relation(name: "NodeBOnAssetRelation")
}rcy
02/21/2018, 7:38 PMit makes it very convenient to query the whole graph like this:
rcy
02/21/2018, 7:40 PM Copy code
allAssetRelations {
dependencies { nodeB { id } }
dependents { nodeA { id } }
}rcy
02/21/2018, 7:41 PMI'm not sure if your direct parent/children relations will work or not. I definitely thought about doing it that way, but went with modeling the relation/edge itself because we need to store other data on it
rcy
02/21/2018, 7:41 PMhth
h
horia.ancas
02/21/2018, 7:41 PMhey, thanks for the quick reply
horia.ancas
02/21/2018, 7:42 PMthat’s an interesting approach that I need to better understand
r
rcy
02/21/2018, 7:42 PMyeah, I'm happy to talk more about it... it took awhile to get to this point, but having great success with it
rcy
02/21/2018, 7:43 PMits still mindbending sometimes with the queries and traversing the graph
h
horia.ancas
02/21/2018, 7:43 PMbefore moving to prisma, I was doing something in the
children()horia.ancas
02/21/2018, 7:44 PMlike mapping over the ids and returning the actual node data
horia.ancas
02/21/2018, 7:44 PMyeah, it’s a bit hard to understand for me 🙂
r
rcy
02/21/2018, 7:44 PMwhat are you trying to model, ultimately?
h
horia.ancas
02/21/2018, 7:45 PMa graph structure 🙂
r
rcy
02/21/2018, 7:45 PMthen I recommend modelling the nodes and the edges as separate models, it will make it sane
horia.ancas
02/21/2018, 7:46 PMsomething like this
horia.ancas
02/21/2018, 7:46 PMbut how do I know which are the nodes at the edges?
r
rcy
02/21/2018, 7:47 PMso each edge (I call AssetRelation in my model), has two endpoints nodeA and nodeB. In my project it is dependencies, so nodeB is a dependency of nodeA
rcy
02/21/2018, 7:48 PMi guess that is a subtlety, maybe. Relations are directed in my project
h
horia.ancas
02/21/2018, 7:49 PMoh, I see what you mean by edges, I was confusing them with leaf nodes 🙄
r
rcy
02/21/2018, 7:50 PMright, nodes boxes, edges lines 🙂
rcy
02/21/2018, 7:50 PMthe nice thing about having edges as a separate model is you can delete that edge and then you have just partitioned your graph
rcy
02/21/2018, 7:50 PMor you can unlink one node and link another to manipulate the tree
h
horia.ancas
02/21/2018, 7:50 PM😐
horia.ancas
02/21/2018, 7:50 PMthat is awesome indeed
r
rcy
02/21/2018, 7:51 PMwhich looks like the kind of thing you might want to do in your project (i am guessing from the drawing)
h
horia.ancas
02/21/2018, 7:51 PMaye, that would be awesome to have
horia.ancas
02/21/2018, 7:51 PMalright, I’ll give it a shot
r
rcy
02/21/2018, 7:52 PMawesome, good luck! ping me if you have any q's, happy to talk more
h
horia.ancas
02/21/2018, 7:52 PMawesome, thank you very much 🙂
2 Views