-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable complex query filters #373
Comments
I like this solution to the problem of long unmanageable mappings. Would it be possible and reasonable to also support subqueries for properties? Happened before (customs declarations among others): substitute some conventional value with the one from a dictionary.
be able to reduce them to something like
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Riffing off of #366, we've been discussing a more advanced filter mechanism in entity mappings both for queries and for schema assignment. I'm sketching this out here to get some feedback.
The basic idea is to make it possible to compile nested complex queries. This might have to be incompatible to the existing
filter
,filter_not
rules in mappings, so we would be introducing a newquery
section (whichfilter
andfilter_not
would be transparently re-written to). The query syntax itself could riff off of the MongoDB syntax, which manages to encapsulate compound queries in JSON.The second purpose of this enhancement would be to make schema conditional on column contents. For example, we often see tables where companies and people are mixed, and whether a row describes a person or company is determined by a value like
individual
/entity
in one column.Here's a sketch of how we could address both issues:
Especially keen for feedback from @uhhhuh @brrttwrks :)
The text was updated successfully, but these errors were encountered: