-
Notifications
You must be signed in to change notification settings - Fork 89
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
RFE: Lookup two field values #43
Comments
hey Viliam, thank you for the idea, sounds interesting. I wonder if references to other fields alone would feel like a self-sufficient feature. I guess that when we use
If we start thinking about it this way, taking into account complex expressions and functions, the scope of the feature starts to look huge. Of course, this is not always the case, and sometimes On one hand, I can understand the need for referencing other fields. On the other hand, I'm afraid that it may be a path down the rabbit hole and may add too much complexity to the library. What do you think? thanks, Denis |
Hello Denis, Your points are very valid. We had a use-case when two dates have been compared, if one precedes the other. I understand that this might not be a very common case, and would lead to more complex structures, as you mentioned. Unless anyone would have another use-case, we can close this issue. |
We'd love to see this. We were also looking for date related comparison - we have an invoice model and were looking for invoices where the |
(Feature Request)
Hello,
Would it be possible to extend the query language to support lookup by other fields value?
For example:
would translate to
The suggestions can also offer the field name in the context where a value is expected.
Thank you for consideration.
The text was updated successfully, but these errors were encountered: