Closed lilactown closed 2 years ago
This is what I propose: we merge the meta from the join and the join vector, and place on the same :meta
in the AST, the join will have priority. What do you think?
Makes sense to me
BTW I have a branch in my project pyramid trying to use this https://github.com/lilactown/pyramid/pull/30
Closing, after discussions we got to the point of not changing the library.
Currently, metadata is preserved in the AST when attached to the top-level query vector, or any child which is a map.
However, it is not preserved on join children
The only exception is a
:component
key, which is for some reason preserved but undocumentedIt would be great to be able to preserve metadata wherever it is in the query. It might be ambiguous where to store it, though; the
:component
way of storing the join children's metadata on the:join
node is what I need for my use case, but that would clobber the way that metadata on the outer map of a join is currently stored.Not sure the exact solution, but wanted to track and get feedback on the problem at least.