@abhimanyusinghgaur: Wow! That was an elaborate reply. Thanks for thinking this through in such depth.
I thought about case 1 as you mentioned and that looks like the simplest one to get it implemented, but then did not move forward with that since I was not sure if it is okay to do that (felt kind of hacky, not sure though)
Case 2 seems interesting (using DQL within GQL) to enable search. Will this just narrow down the search within the attributes of that entity without checking other entities? That can speed up a lot of time taken for search.
And finally case 3 definitely looks way cleaner. Looking forward to something like that so that we can have the uniqueness constrained within the children alone rather than having it globally.
Btw, while unrelated to this topic, I really have to commend the effort of the Dgraph team in the way all of you stick around to help the community and I really appreciate the effort you are putting in to make Dgraph great.
I even happened to see this: Devotee badge on Discuss Dgraph and that takes some real devotion. @MichelDiz visiting 1 year continuously.
Not just this, I even see people from the community like @amaster507 and @abhijit-kar hanging around to help which is really great to see.
I am really new to Dgraph (have been using it for past 3 days I guess and I have already completed work with the DB schema and all queries related to it which really shows the speed at which we can get things done and that’s great)
Thanks again. Have never run Dgraph in production, planning to do it soon. Fingers crossed