Looking into adding “tags” into my project as shown here
https://github.com/dgraph-io/graphoverflow/blob/master/schema.txt. (in my case “topics”)
Graphoverflow is a very nice example Michel showed me, yet I’m wondering why this structure is used:
Tags: uid @reverse . Tag: uid @reverse . Tag.text: string @index(hash) .
Specifically, wouldn’t it be more simple when you know each tag or topic will be unique and just do this:
Tags: uid @ reverse Tag: string @index(hash) .
Why/When would I want to design the schema like shown in Graphoverflow?