Open thelinuxlich opened 9 years ago
This would be useful for things like https://github.com/rethinkdb/rethinkdb/issues/4397 .
I think it would need to be an optional feature for a given table, since some users have dynamically generated keys and the number of keys used might grow unboundedly.
Putting into backlog for now, we should look at it when we have decided on a solution for #4397.
Yeah I think it should be configured on table creation
Right now if I need this I would have to iterate all records which is not performant:
And it lacks nested keys information. It would be nice if RethinkDB stored this information as metadata easily accessible for us. Furthermore, the user could configure this "field capture" on a index basis.