Details
-
Improvement
-
Resolution: Fixed
-
Major
-
6.6.2, 6.5.2, Cheshire-Cat
-
1
Description
The idea behind this is to provide a function which only provides fields that match a certain name at any level within a document.
Pasting the slack discussion I had with Marco about this:
Tim Bradgate 17:52
So maybe this is a horrible question, but how plausible would it be to allow N1QL to do something like select *.b from a where c… , and return the list of paths *.b which match the pattern? So if you didn’t know the nesting level of your data for exampleMarco Greco 17:54
yawser
17:54
let me get my head round that
17:54
you basically want to find any field in your document that has a b subdocumentTim Bradgate 17:56
I’m not saying I want to :wink:
But yes, was thinking about this the other night, could have two ways of doing it, so a..c which matches the path at a single level, and then a.*.c (ant style) to match any depth path from a to cMarco Greco 17:56
from a planning and projection point of view that would be a nightmareTim Bradgate 17:57
This basically came from, an API is giving me some data about something, but doesn’t tell you in what structure that data appears in. So I know all the field names, but not their paths in the resulting documentMarco Greco 17:57
you probably want some field search function