The only way I can think of to pull this simple query off in current Dgraph Slash is to change schema like below:
type Object {
id: ID!
name: String @search(by:[fulltext])
anotherObject: AnotherObject! @hasInverse(field:object)
}
type AnotherObject {
id: ID!
name: String @search(by:[fulltext])
object: Object @hasInverse(field:anotherObject)
}
And then query AnotherObject where ID = 0x123 and return related Objects filtered by Name = "Some search term string.” I’m assuming this may be possible.
And I’ll have to figure out how to retroactively fix all my current data: how to relate all these existing Objects & AnotherObjects efficiently, especially since I can’t currently query based on the info I need to filter them! Ha.
And I’m not sure exactly how Badger structures data, but it seems like this (otherwise not needed?) inverse requirement may effectively double the size of my data? (But maybe improve search performance?)
Is there’s another way? Thanks.