-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Querying aliases feature #5321
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
Comments
|
any progress? |
Nope not yet |
Anu updates on this? |
@rafaelcorreiapoli no, not yet. Will bump this up for the next minor version. |
I didn't quite read this thread carefully, it looks like this was fixed by #5338. Here's the docs for |
Following #5184, I now want to implement the ability to query (and update) based on aliased fields. I've been looking at the code for a while. At first, I was looking for ways to apply an option for aliasing on each and every model query. But then, I came up with another solution, which looks something like:
Which I think is neater, clearer, and obviously optional. Plus, this won't change our codebase too much, avoiding cases when we forgot to do conditions aliasing in some queries.
I want to know if you feel okay going down this approach, so I put it here for feedback
The text was updated successfully, but these errors were encountered: