Late reply, busy sorry and computer died etc.
Anyhow,
In the context of the question (giving nodes a type, see OP) I’d filter by “has predicate is_community”
Would I need to index this predicate in this use case?
And I know it’s hard to predict the future, however maybe you have a plan.
Do you expect the way inserts, updates, queries and deletes are done to change?
aka. if I wrote a http api with dgraph as storage how likely is it that I’d have to rewrite both the app and the way I do CRUD once 1.0 is out?
Regarding uint64 id, if I understood correctly,
When I do
p := new(Person)
p.Uid = bson.NewObjectId().Hex()
this would be the unique identifier and not an uint64 value.
An uint64 value would only be assigned when .pUid == “” and then this value would be converted to string when querying.
I’m still concerned about the value overflowing.
uint64 maybe large but it’s not that large when every transaction, every query receive their own uint64 id( that seems to be serial).
Imagine a semi busy social network/dating site with 10k members all uploading fotos and sending messages and doing queries and searches